CVE-2026-59868

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 52% 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, 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: 1%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 before 5.2.0, when merge keys are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in version 5.2.0.

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
1%
EPSS %ILE
48%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 13, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

YAML merge-key chains can force quadratic CPU consumption in js-yaml · Advisory · nodeca/js-yaml · GitHub

https://github.com/nodeca/js-yaml/security/advisories/GHSA-g796-fgmg-93mv
github_commit

commit 3105455b81de (nodeca/js-yaml)

Fix landed in nodeca/js-yaml commit 3105455b81de — awaiting tagged release

https://github.com/nodeca/js-yaml/commit/3105455b81dee69e0fd36e09ac0b2ccfdb54adc1

Vendor Advisories for CVE-2026-59868(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
redhatnodejs22-main-22.23.1-2.hum12026-07-03redhat
redhatrust-main-1.96.1-1.hum12026-07-02redhat
redhatnodejs24-main-24.18.0-0.2.hum12026-07-01redhat
redhatnodejs26-main-26.4.0-1.3.hum12026-06-30redhat
redhatdotnet8-0-main-8.0.128-1.hum12026-06-18redhat
redhatnodejs20-main-20.20.2-1.hum12026-04-21redhat
redhatyarnpkg-main-1.22.22-18.1.hum12026-04-11redhat
redhatnodejs25-main-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 rangeFixed inDependents
js-yaml—5.2.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 109× 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 157 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-59868?
CVE-2026-59868 is a high vulnerability published on July 8, 2026. js-yaml is a JavaScript YAML parser and dumper. From 5.0.0 before 5.2.0, when merge keys are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in…
When was CVE-2026-59868 disclosed?
CVE-2026-59868 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59868 actively exploited?
CVE-2026-59868 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.9% of all scored CVEs.
What is the CVSS score of CVE-2026-59868?
CVE-2026-59868 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59868?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59868, 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-59868

Explore →

Is Your Infrastructure Affected by CVE-2026-59868?

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

Start Free Scan →Browse All CVEs