CVE-2026-73643

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-58185 (ENISA EUVD) · GHSA-pm4m-ph32-ghv5 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-06). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 24, 2026

Last Modified

October 24, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Exponential 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-ghv5
GitHub commit

commit 3e5240f9cbe6 (nodeca/js-yaml)

Fix landed in nodeca/js-yaml commit 3e5240f9cbe6 — awaiting tagged release

https://github.com/nodeca/js-yaml/commit/3e5240f9cbe645ce5afb58524954a13c8539c853

Patch Availability(20)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
js-yaml—
  • 5.0.0 up to 5.2.2: fixed in 5.2.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 172 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 72 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-11-06 23:41 UTCEchelonGraph re-scored
  8. 2026-11-06 23:41 UTCVendor advisory
  9. 2026-11-06 23:41 UTCGHSA enrichmentGHSA-pm4m-ph32-ghv5 · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-11-01 07:39 UTCGHSA enrichmentGHSA-pm4m-ph32-ghv5 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-01 07:39 UTCEchelonGraph re-scored
  17. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-31 07:35 UTCEchelonGraph re-scored
  19. 2026-10-31 07:35 UTCVendor advisory
  20. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
Show 75 more
  1. 2026-10-25 14:05 UTCEchelonGraph re-scored
  2. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-24 15:27 UTCVendor advisory
  4. 2026-10-23 18:26 UTCEchelonGraph re-scored
  5. 2026-10-23 18:26 UTCVendor advisory
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-20 08:27 UTCEchelonGraph re-scored
  11. 2026-10-20 08:27 UTCVendor advisory
  12. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-18 03:15 UTCEchelonGraph re-scored
  15. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-13 07:51 UTCEchelonGraph re-scored
  21. 2026-10-13 07:51 UTCVendor advisory
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-12 15:40 UTCEchelonGraph re-scored
  24. 2026-10-11 19:26 UTCEchelonGraph re-scored
  25. 2026-10-11 16:42 UTCEchelonGraph re-scored
  26. 2026-10-11 14:01 UTCEchelonGraph re-scored
  27. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  33. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  34. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-10-04 07:42 UTCEchelonGraph re-scored
  36. 2026-10-04 07:42 UTCVendor advisory
  37. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-10-03 03:18 UTCEchelonGraph re-scored
  39. 2026-10-03 03:18 UTCVendor advisory
  40. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-10-01 05:59 UTCEchelonGraph re-scored
  42. 2026-10-01 05:59 UTCVendor advisory
  43. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-09-28 04:26 UTCEchelonGraph re-scored
  46. 2026-09-28 04:26 UTCVendor advisory
  47. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  48. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  49. 2026-09-25 10:04 UTCEchelonGraph re-scored
  50. 2026-09-25 10:04 UTCVendor advisory
  51. 2026-09-24 00:55 UTCEchelonGraph re-scored
  52. 2026-09-24 00:55 UTCVendor advisory
  53. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  54. 2026-09-23 10:56 UTCVendor advisory
  55. 2026-09-22 22:11 UTCEchelonGraph re-scored
  56. 2026-09-22 22:11 UTCVendor advisory
  57. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  58. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  59. 2026-09-20 01:39 UTCEchelonGraph re-scored
  60. 2026-09-20 01:39 UTCVendor advisory
  61. 2026-09-18 20:35 UTCEchelonGraph re-scored
  62. 2026-09-18 20:35 UTCVendor advisory
  63. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  64. 2026-09-18 02:58 UTCEchelonGraph re-scored
  65. 2026-09-18 02:58 UTCVendor advisory
  66. 2026-09-17 01:58 UTCEchelonGraph re-scored
  67. 2026-09-17 01:58 UTCVendor advisory
  68. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  69. 2026-09-16 06:39 UTCEchelonGraph re-scored
  70. 2026-09-16 06:39 UTCVendor advisory
  71. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  72. 2026-09-15 09:35 UTCEchelonGraph re-scored
  73. 2026-09-15 09:35 UTCVendor advisory
  74. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  75. 2026-09-14 10:45 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-73643?
CVE-2026-73643 is a high-severity vulnerability; its CVE record was published on July 24, 2026. 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…
When was the CVE record for CVE-2026-73643 published?
The CVE record for CVE-2026-73643 was published on July 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-73643 actively exploited?
CVE-2026-73643 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73643?
CVE-2026-73643 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73643?
A fix for CVE-2026-73643 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73643 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73643

Explore →

Is Your Infrastructure Affected by CVE-2026-73643?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.