Denial of Service in js-yaml
Priority LOW 38CWE-400Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-400.
Summary
Versions of `js-yaml` prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service. ## Recommendation Upgrade to version 3.13.0.
Why it matters now
Fix Fixed js-yaml (npm): 3.13.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 |
|---|---|---|---|---|---|
| — | js-yaml (npm) | before 3.13.0 | 3.13.0 | Patch available | GHSA-2pr6-76vf-7546 |
- js-yaml (npm) Vendor— Affected before 3.13.0 Fixed in 3.13.0 Patch available GHSA-2pr6-76vf-7546
Remediation
- Fix · GHSA-2pr6-76vf-7546 js-yaml (npm) Fixed in 3.13.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-2pr6-76vf-7546
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences