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.3%, top 72% 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).

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%CVSS: 7.5Exploit: Elevated riskExposed: 0

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.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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

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.
github Patch Available🟡 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(9)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
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:17878373082026-09-01redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17875903722026-09-01redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17877448432026-09-01redhat
redhatdiscovery/discovery-ui-rhel9:17882061962026-08-31redhat
redhatcluster-observability-operator/monitoring-console-plugin-pf6-rhel9:17875975782026-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 rangeFixed inDependents
js-yaml—5.2.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 69× 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.

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 72.0% of all scored CVEs.
What is the CVSS score of CVE-2026-73643?
CVE-2026-73643 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-73643?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73643, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs