devalue `uneval`ed code can create objects with polluted prototypes when `eval`ed
Priority LOW 38CWE-1321Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Under certain circumstances, `uneval`ing untrusted data can produce output code that will create objects with polluted prototypes when later `eval`ed, meaning the output data can be a different shape from the input data.
Why it matters now
Fix Fixed devalue (npm): 5.6.3
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | devalue (npm) | before 5.6.3 | 5.6.3 | Patch available | GHSA-8qm3-746x-r74r |
- devalue (npm) Vendor— Affected before 5.6.3 Fixed in 5.6.3 Patch available GHSA-8qm3-746x-r74r
Remediation
- Fix · GHSA-8qm3-746x-r74r devalue (npm) Fixed in 5.6.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-8qm3-746x-r74r
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences