CVE-2026-59870

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6% (49th 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, nvd
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.7%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

js-yaml is a JavaScript YAML parser and dumper. Prior to 3.15.1, 4.3.1, and 5.2.1, YAML11_SCHEMA support for the !!omap tag in src/tag/sequence/omap.ts uses omapTag.addItem() to perform a linear duplicate-key scan on every insertion, causing O(n^2) CPU consumption when yaml.load() parses a crafted ordered-map document. In v3 and v4, !!omap is active and exploitable by default. v5 doesn't use !!omap by default, and the chances of activating it are very low.This issue is fixed in 3.15.1, 4.3.1, and 5.2.1.

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.7%
EPSS %ILE
53rd
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 8, 2026

Last Modified

October 6, 2026

Advisory Details (2)

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

Quadratic-complexity (O(n^2)) DoS in js-yaml 5.x via !!omap tag in YAML11_SCHEMA · Advisory · nodeca/js-yaml · GitHub

https://github.com/nodeca/js-yaml/security/advisories/GHSA-724g-mxrg-4qvm
github_commit

commit 39f3211a2f01 (nodeca/js-yaml)

Fix landed in nodeca/js-yaml commit 39f3211a2f01 — awaiting tagged release

https://github.com/nodeca/js-yaml/commit/39f3211a2f01b3c6982710cf21434ab7060acefe

Vendor Advisories for CVE-2026-59870(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 / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs22-main-10.9.8-1.22.23.1.2.hum12026-07-03redhat
redhatrust-main-1.96.1-1.hum12026-07-02redhat
redhatnodejs24-main-11.16.0-1.24.18.0.0.2.hum12026-07-01redhat
redhatnodejs26-main-11.17.0-1.26.4.0.1.3.hum12026-06-30redhat
redhatdotnet8-0-main-8.0.128-1.hum12026-06-18redhat
redhatnodejs20-main-10.8.2-1.20.20.2.1.hum12026-04-21redhat
redhatyarnpkg-main-1.22.22-18.1.hum12026-04-11redhat
redhatnodejs25-main-11.12.1-1.25.9.0.1.1.hum12026-04-10redhat

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.1: fixed in 5.2.1
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-59870?
CVE-2026-59870 is a high vulnerability published on July 8, 2026. js-yaml is a JavaScript YAML parser and dumper. Prior to 3.15.1, 4.3.1, and 5.2.1, YAML11_SCHEMA support for the !!omap tag in src/tag/sequence/omap.ts uses omapTag.addItem() to perform a linear duplicate-key scan on every insertion, causing O(n^2) CPU consumption when yaml.load() parses a crafted…
When was CVE-2026-59870 disclosed?
CVE-2026-59870 was first published on July 8, 2026, with the most recent update on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59870 actively exploited?
CVE-2026-59870 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59870?
CVE-2026-59870 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59870?
A fix for CVE-2026-59870 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59870 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-59870

Explore →

Is Your Infrastructure Affected by CVE-2026-59870?

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

Book a Demo →Browse All CVEs