CVE-2025-57820
BaseFortify
Publication date: 2025-08-26
Last updated on: 2025-08-29
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sveltejs | devalue | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1321 | The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Svelte devalue utility library prior to version 5.3.2. When a string passed to devalue.parse represents an object containing a __proto__ property, and the function does not verify that an index is numeric, it can lead to prototype pollution. This means an attacker could manipulate the prototype of objects, potentially altering their behavior or properties unexpectedly.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to perform prototype pollution, which may lead to unexpected behavior in applications using the affected library. This could result in security issues such as privilege escalation, data manipulation, or application crashes depending on how the polluted prototypes are used within the application.
What immediate steps should I take to mitigate this vulnerability?
Upgrade the Svelte devalue library to version 5.3.2 or later, as this version contains the fix for the prototype pollution vulnerability in devalue.parse.