Denial of Service in serialize-to-js
Priority LOW 38Published · 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
Versions of `serialize-to-js` prior to 2.0.0 are vulnerable to Denial of Service. User input is not properly validated, allowing attackers to provide inputs that lead the execution to loop indefinitely. ## Recommendation Upgrade to version 2.0.0 or later.
Why it matters now
Fix Fixed serialize-to-js (npm): 2.0.0
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 |
|---|---|---|---|---|---|
| — | serialize-to-js (npm) | before 2.0.0 | 2.0.0 | Patch available | GHSA-w5q7-3pr9-x44w |
- serialize-to-js (npm) Vendor— Affected before 2.0.0 Fixed in 2.0.0 Patch available GHSA-w5q7-3pr9-x44w
Remediation
- Fix · GHSA-w5q7-3pr9-x44w serialize-to-js (npm) Fixed in 2.0.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-w5q7-3pr9-x44w
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences