Prototype pollution via unchecked deserialized object keys
Published Aug 26, 2025 · Updated Aug 27, 2025
Prototype pollution in Svelte devalue before 5.3.2 allows remote attackers to alter object behavior through crafted serialized input. The parse and unflatten hydration loop accepts proto keys and nonnumeric array indices, then assigns the resulting values to object properties. Exploitation requires a consuming application to pass attacker-controlled serialized data to these APIs; successful input can overwrite properties and bypass server-side validation.
Summary
What happened
Prototype pollution in Svelte devalue before 5.3.2 allows remote attackers to alter object behavior through crafted serialized input. The parse and unflatten hydration loop accepts proto keys and nonnumeric array indices, then assigns the resulting values to object properties. Exploitation requires a consuming application to pass attacker-controlled serialized data to these APIs; successful input can overwrite properties and bypass server-side validation.
The record
- CVE
- CVE-2025-57820
- Published
- Aug 26, 2025
- Updated
- Aug 27, 2025
- Vendor
- Svelte
- Product
- devalue
- Classifications
- CWE-1321, CAPEC-180, CAPEC-77, CAPEC-1
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory proof-of-concept payloadsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo