js-yaml is a JavaScript YAML parser and dumper. From 5.0.0 until 5.2.2, parsing a small YAML document can take exponential time when an application calls load() or loadAll() on untrusted input. In src/parser/parser.ts, readFlowCollection uses restoreState and calls parseNode a second time when a flow-sequence entry is recognized as a key: value pair. If the key is a nested flow sequence of the same shape, every level is parsed twice, causing O(2^n) work and allowing an input under 200 bytes to keep one CPU busy for minutes, block the Node.js event loop, and stall the process. No anchors, aliases, merges, tags, or nondefault options are required. This issue is fixed in version 5.2.2.
CVE-2026-73643
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 13, 2026Exponential parsing time in js-yaml flow collections leads to denial of service · Advisory · nodeca/js-yaml · GitHub
https://github.com/nodeca/js-yaml/security/advisories/GHSA-pm4m-ph32-ghv5commit 3e5240f9cbe6 (nodeca/js-yaml)
Fix landed in nodeca/js-yaml commit 3e5240f9cbe6 — awaiting tagged release
https://github.com/nodeca/js-yaml/commit/3e5240f9cbe645ce5afb58524954a13c8539c853Vendor Advisories for CVE-2026-73643(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| js-yaml | — | 5.2.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 19:11 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 18:05 UTCEG score recompute
- 2026-08-23 03:31 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 02:29 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 00:52 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 23:51 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 22:49 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 21:37 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 20:36 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:05 UTCEG score recompute
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 07:04 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 17:36 UTCEG score recompute
- 2026-08-14 17:12 UTCEG score recompute
Show 2 moreShow fewer
- 2026-08-13 18:19 UTCEG score recompute
- 2026-08-13 17:52 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-73643?
When was CVE-2026-73643 disclosed?
Is CVE-2026-73643 actively exploited?
What is the CVSS score of CVE-2026-73643?
How do I remediate CVE-2026-73643?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73643
Is Your Infrastructure Affected by CVE-2026-73643?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.