CVE-2026-73643

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: Elevated riskExposed 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/100CISA SSVC

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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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
40th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 24, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
githubMentions a patch (unverified)🟡 PoC Available

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

Vendor Advisories for CVE-2026-73643(16)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/nmstate-console-plugin-rhel9:17899376432026-10-01redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17899040882026-10-01redhat
redhatrhmtc/openshift-migration-ui-rhel8:17895463732026-09-17redhat
redhatrhem/flightctl-ui-ocp-rhel9:17894864462026-09-16redhat
redhatrhem/flightctl-ui-rhel9:17894867502026-09-16redhat
redhatrhem/flightctl-ui-rhel10:17894861812026-09-16redhat
redhatrhem/flightctl-ui-rhel10:17894881112026-09-16redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17883122212026-09-09redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17889435312026-09-09redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17877448432026-09-01redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17878373082026-09-01redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17875903722026-09-01redhat
redhatcluster-observability-operator/monitoring-console-plugin-pf6-rhel9:17875975782026-08-31redhat
redhatdiscovery/discovery-ui-rhel9:17882061962026-08-31redhat

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 / 60× 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.

Showing the most recent 100 of 119 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 07:42 UTCEG score recompute
  8. 2026-10-04 07:42 UTCVendor advisory
  9. 2026-10-03 14:26 UTCEPSS rescore
  10. 2026-10-03 03:18 UTCEG score recompute
  11. 2026-10-03 03:18 UTCVendor advisory
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-10-01 05:59 UTCEG score recompute
  14. 2026-10-01 05:59 UTCVendor advisory
  15. 2026-09-29 15:24 UTCEPSS rescore
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 04:26 UTCEG score recompute
  18. 2026-09-28 04:26 UTCVendor advisory
  19. 2026-09-27 13:48 UTCEPSS rescore
  20. 2026-09-26 15:59 UTCEPSS rescore
  21. 2026-09-25 10:04 UTCEG score recompute
  22. 2026-09-25 10:04 UTCVendor advisory
  23. 2026-09-24 00:55 UTCEG score recompute
  24. 2026-09-24 00:55 UTCVendor advisory
  25. 2026-09-23 17:54 UTCEPSS rescore
Show 75 more
  1. 2026-09-23 10:56 UTCVendor advisory
  2. 2026-09-22 22:11 UTCEG score recompute
  3. 2026-09-22 22:11 UTCVendor advisory
  4. 2026-09-21 21:09 UTCEPSS rescore
  5. 2026-09-20 20:16 UTCEPSS rescore
  6. 2026-09-20 01:39 UTCEG score recompute
  7. 2026-09-20 01:39 UTCVendor advisory
  8. 2026-09-18 20:35 UTCEG score recompute
  9. 2026-09-18 20:35 UTCVendor advisory
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 02:58 UTCEG score recompute
  12. 2026-09-18 02:58 UTCVendor advisory
  13. 2026-09-17 01:58 UTCEG score recompute
  14. 2026-09-17 01:58 UTCVendor advisory
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 06:39 UTCEG score recompute
  17. 2026-09-16 06:39 UTCVendor advisory
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-15 09:35 UTCEG score recompute
  20. 2026-09-15 09:35 UTCVendor advisory
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-14 10:45 UTCVendor advisory
  23. 2026-09-13 22:14 UTCEG score recompute
  24. 2026-09-13 22:14 UTCVendor advisory
  25. 2026-09-13 06:13 UTCVendor advisory
  26. 2026-09-12 17:41 UTCEG score recompute
  27. 2026-09-12 17:41 UTCVendor advisory
  28. 2026-09-12 15:02 UTCEPSS rescore
  29. 2026-09-12 05:07 UTCVendor advisory
  30. 2026-09-11 16:36 UTCEG score recompute
  31. 2026-09-11 16:36 UTCVendor advisory
  32. 2026-09-11 14:53 UTCEPSS rescore
  33. 2026-09-11 02:32 UTCVendor advisory
  34. 2026-09-10 13:35 UTCEG score recompute
  35. 2026-09-10 13:35 UTCVendor advisory
  36. 2026-09-10 09:35 UTCEPSS rescore
  37. 2026-09-09 08:44 UTCEG score recompute
  38. 2026-09-09 08:44 UTCVendor advisory
  39. 2026-09-08 22:01 UTCEPSS rescore
  40. 2026-09-07 21:23 UTCEG score recompute
  41. 2026-09-07 21:23 UTCVendor advisory
  42. 2026-09-06 13:48 UTCEPSS rescore
  43. 2026-09-06 08:10 UTCVendor advisory
  44. 2026-09-05 19:23 UTCEG score recompute
  45. 2026-09-05 19:23 UTCVendor advisory
  46. 2026-09-05 06:53 UTCEG score recompute
  47. 2026-09-05 06:53 UTCVendor advisory
  48. 2026-09-04 12:49 UTCEG score recompute
  49. 2026-09-04 12:49 UTCVendor advisory
  50. 2026-09-04 05:07 UTCEPSS rescore
  51. 2026-09-02 14:12 UTCEPSS rescore
  52. 2026-09-01 23:15 UTCEG score recompute
  53. 2026-09-01 23:15 UTCVendor advisory
  54. 2026-09-01 13:54 UTCEPSS rescore
  55. 2026-09-01 04:40 UTCEPSS rescore
  56. 2026-09-01 04:40 UTCEPSS rescore
  57. 2026-08-31 01:25 UTCEG score recompute
  58. 2026-08-30 19:18 UTCEPSS rescore
  59. 2026-08-30 19:17 UTCEPSS rescore
  60. 2026-08-30 12:54 UTCEG score recompute
  61. 2026-08-30 01:22 UTCEPSS rescore
  62. 2026-08-30 00:16 UTCEG score recompute
  63. 2026-08-28 21:42 UTCEPSS rescore
  64. 2026-08-27 22:29 UTCEG score recompute
  65. 2026-08-27 14:25 UTCEPSS rescore
  66. 2026-08-26 20:19 UTCEG score recompute
  67. 2026-08-26 14:47 UTCEPSS rescore
  68. 2026-08-25 19:11 UTCEG score recompute
  69. 2026-08-25 13:49 UTCEPSS rescore
  70. 2026-08-24 18:05 UTCEG score recompute
  71. 2026-08-23 03:31 UTCEG score recompute
  72. 2026-08-23 00:19 UTCEPSS rescore
  73. 2026-08-22 02:29 UTCEG score recompute
  74. 2026-08-21 23:49 UTCEPSS rescore
  75. 2026-08-21 00:52 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-73643?
CVE-2026-73643 is a high vulnerability 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 CVE-2026-73643 disclosed?
CVE-2026-73643 was first published on July 24, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (40th 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.

Book a Demo →Browse All CVEs