CVE-2026-84375

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-69712 (ENISA EUVD) · GHSA-2883-xcg3-v3hh (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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2, 4.3.2, and 5.4.1, maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while processing the merge key <<. An attacker can alias a large sequence of empty mappings into many merge targets, causing O(N * K) processing while totalMergeKeys remains unchanged and the configured resource limit is never reached. A relatively small YAML document can therefore cause prolonged CPU consumption in applications that parse untrusted YAML, and merge processing is enabled by default on these release lines. In v3 & v4, merge is enabled by default so the severity score is higher. This issue is fixed in versions 3.15.2, 4.3.2, and 5.4.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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
45th
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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: 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 none (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.

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

September 1, 2026

Last Modified

September 28, 2026

Advisory Details (5)

Auto-updated Sep 1, 2026
Patch available. Sources: github, github_pr, github_commit.
GitHub commit

commit d90b6612a5a8 (nodeca/js-yaml)

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

https://github.com/nodeca/js-yaml/commit/d90b6612a5a84385bdcb556c44578eac76dc0f6b
GitHub commit

commit 6a8e05f9a485 (nodeca/js-yaml)

Fix landed in nodeca/js-yaml commit 6a8e05f9a485 — awaiting tagged release

https://github.com/nodeca/js-yaml/commit/6a8e05f9a485188ed730ac81e81ae221352ef480
GitHub commit

commit 3485bc06ff8a (nodeca/js-yaml)

Fix landed in nodeca/js-yaml commit 3485bc06ff8a — awaiting tagged release

https://github.com/nodeca/js-yaml/commit/3485bc06ff8a0251505f44a00414d90df2466639
GitHub pull request

fix: count empty merge sources against maxTotalMergeKeys

Fix merged in nodeca/js-yaml PR #797 on 2026-08-26 — awaiting tagged release

https://github.com/nodeca/js-yaml/pull/797
GitHub advisoryMentions a patch (unverified)

maxTotalMergeKeys does not limit CPU use for empty merge sources · Advisory · nodeca/js-yaml · GitHub

https://github.com/nodeca/js-yaml/security/advisories/GHSA-2883-xcg3-v3hh

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17917882672026-10-19redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17908280122026-10-15redhat
redhatrhtas/rekor-search-ui-rhel9:17915343392026-10-15redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17918656602026-10-13redhat
redhatrhdh/rhdh-hub-rhel9:17913114952026-10-08redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:17912496402026-10-06redhat
redhatrhoai/odh-mlflow-rhel9:17896536062026-09-30redhat
redhatansible-automation-platform/automation-portal:17902549632026-09-28redhat
redhatansible-automation-platform/automation-portal:17902564052026-09-28redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17896858372026-09-23redhat
redhatautomation-platform-ui-0:2.6.14-1.el9ap2026-09-23redhat
redhatnetwork-observability/network-observability-console-plugin-rhel9:17899782772026-09-23redhat
redhatansible-automation-platform-tech-preview/mcp-server-rhel9:17896690362026-09-23redhat
redhatcontainer-native-virtualization/kubevirt-console-plugin-rhel9:17897011682026-09-22redhat
redhatcontainer-native-virtualization/kubevirt-console-plugin-rhel9:17897034762026-09-22redhat
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatcontainer-native-virtualization/kubevirt-console-plugin:17896246562026-09-22redhat
redhatdiscovery/discovery-ui-rhel9:17896774592026-09-21redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
redhatopenshift-service-mesh/kiali-rhel9:17890845852026-09-17redhat
redhatsatellite/iop-remediations-rhel9:17896150952026-09-17redhat
redhatrhmtc/openshift-migration-ui-rhel8:17895463732026-09-17redhat
redhatdevspaces/openvsx-rhel9:17891442692026-09-17redhat
redhatopenshift-service-mesh/kiali-rhel9:17890273952026-09-17redhat
redhatsatellite/iop-remediations-rhel9:17896155932026-09-17redhat
redhatopenshift-service-mesh/kiali-rhel9:17890248272026-09-17redhat
redhatopenshift-service-mesh/kiali-rhel9:17890221732026-09-17redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595652026-09-17redhat
redhatopenshift-service-mesh/kiali-rhel9:17890213192026-09-17redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595732026-09-17redhat

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-js-yaml4.1.0+dfsg+~4.0.5-7, 4.1.1+dfsg+~4.0.9-1, 4.2.0+~4.0.9-1, 4.2.0+~4.0.9-2, 4.3.2+~4.0.9-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-js-yaml4.1.0+dfsg+~4.0.5-7, 4.1.1+dfsg+~4.0.9-1, 4.2.0+~4.0.9-1, 4.2.0+~4.0.9-2, 4.3.2+~4.0.9-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-js-yaml4.1.0+dfsg+~4.0.5-7, 4.1.1+dfsg+~4.0.9-1, 4.2.0+~4.0.9-1, 4.2.0+~4.0.9-2
  • every version up to 4.3.2+~4.0.9-1: fixed in 4.3.2+~4.0.9-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
js-yaml—
  • 4.0.0 up to 4.3.2: fixed in 4.3.2
  • 3.0.0 up to 3.15.2: fixed in 3.15.2
—

Weakness Classification(2)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 78× 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 it from the CNA feed. 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). Most recent first.

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

Frequently asked(5)

What is CVE-2026-84375?
CVE-2026-84375 is a high-severity vulnerability; its CVE record was published on September 1, 2026. js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2, 4.3.2, and 5.4.1, maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while processing the merge key <<. An attacker can alias a large sequence of empty mappings into many merge…
When was the CVE record for CVE-2026-84375 published?
The CVE record for CVE-2026-84375 was published on September 1, 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 September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-84375 actively exploited?
CVE-2026-84375 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84375?
CVE-2026-84375 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-84375?
A fix for CVE-2026-84375 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84375 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-84375

Explore →

Is Your Infrastructure Affected by CVE-2026-84375?

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