CVE-2025-57820: sveltejs devalue · Prototype Pollution
Affects sveltejs devalueSource CVE Database V5
Not known to be exploited · CVSS 7.9 High : upgrade to 5.3.2 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.3.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade sveltejs devalue to 5.3.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| sveltejs devalue | Affected
| Fixed in
|
AI-suggested
European organizations should take the following specific and practical steps to mitigate this vulnerability: 1) Identify all applications and services using the devalue library, particularly versions prior to 5.3.2, through software inventory and dependency analysis tools. 2) Immediately upgrade the devalue library to version 5.3.2 or later, which contains the fix for prototype pollution. 3) Audit application code to ensure that untrusted input is never directly passed to devalue.parse without validation or sanitization. Implement input validation layers that explicitly reject or sanitize '__proto__' properties and non-numeric indices before parsing. 4) Employ runtime application self-protection (RASP) or Web Application Firewall (WAF) rules that detect and block payloads attempting prototype pollution patterns, such as those containing '__proto__' keys. 5) Conduct thorough testing and code reviews focusing on deserialization and parsing logic to detect similar prototype pollution risks elsewhere in the codebase. 6) Monitor security advisories and threat intelligence feeds for any emerging exploits targeting this vulnerability and prepare incident response plans accordingly. 7) Educate development teams about secure coding practices related to object prototype manipulation and the risks of prototype pollution to prevent recurrence.
Description
Svelte devalue is a utility library. Prior to version 5.3.2, a string passed to devalue.parse could represent an object with a __proto__ property and devalue.parse does not check that an index is numeric. This could result in assigning prototypes to objects and properties, leading to prototype pollution. This issue has been fixed in version 5.3.2