js-yaml is a JavaScript YAML parser and dumper. In js-yaml before 4.1.1 and 3.14.2, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (__proto__). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1 and 3.14.2. Users can protect against this kind of attack on the server by using node --disable-proto=delete or deno (in Deno, pollution protection is on by default).
CVE-2025-64718
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 39EG Risk 39/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)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 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.4%
- EPSS %ILE
- 35th
- 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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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
November 13, 2025
Last Modified
October 7, 2026
Advisory Details (5)
Auto-updated Oct 8, 2026js-yaml has prototype pollution in merge (<<) · CVE-2025-64718 · GitHub Advisory Database · GitHub
https://github.com/advisories/GHSA-mh29-5h37-fv8mPrototype pollution in merge (<<) · Advisory · nodeca/js-yaml · GitHub
https://github.com/nodeca/js-yaml/security/advisories/GHSA-mh29-5h37-fv8mWilling to publish v3 version with CVE fix? · Issue #730 · nodeca/js-yaml · GitHub
https://github.com/nodeca/js-yaml/issues/730#issuecomment-3549635876commit 5278870a1745 (nodeca/js-yaml)
Fix landed in nodeca/js-yaml commit 5278870a1745 — awaiting tagged release
https://github.com/nodeca/js-yaml/commit/5278870a17454fe8621dbd8c445c412529525266commit 383665ff4248 (nodeca/js-yaml)
Fix landed in nodeca/js-yaml commit 383665ff4248 — awaiting tagged release
https://github.com/nodeca/js-yaml/commit/383665ff4248ec2192d1274e934462bb30426879Vendor Advisories for CVE-2025-64718(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:83548Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Ceph Storage
- RHSA-2026:56431Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.18.27 security, enhancement & bug fix update
- RHSA-2026:26411Red Hat Product SecurityHigh
Red Hat Security Advisory: New container image: rhceph-9.0
- RHSA-2026:15979Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Ceph Storage
Patch Availability(4)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | rhceph/grafana-rhel9:1791450715 | 2026-10-15 | redhat |
| redhat | odf4/rook-ceph-rhel9-operator:1786706880 | 2026-08-18 | redhat |
| redhat | rhceph/grafana-rhel10:1781018768 | 2026-06-16 | redhat |
| redhat | rhceph/grafana-rhel9:1777566546 | 2026-05-11 | redhat |
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
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-js-yaml | 3.14.1+dfsg+~3.12.6-2 ... 4.2.0+~4.0.9-1 (10 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-js-yaml | 4.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 |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-js-yaml | 4.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 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-js-yaml | 4.1.0+dfsg+~4.0.5-7 |
| — |
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| js-yaml | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 37× 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 94 of 185 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-23 13:19 UTCEG score recompute
- 2026-10-23 13:19 UTCVendor advisory
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-18 05:20 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-12 16:49 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-11 20:24 UTCEG score recompute
- 2026-10-11 18:36 UTCEG score recompute
- 2026-10-11 15:10 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-07 21:32 UTCEG score recompute
Show 69 moreShow fewer
- 2026-10-07 21:32 UTCVendor advisory
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-02 01:10 UTCOSV refresh
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-12 18:06 UTCOSV refresh
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-24 23:44 UTCOSV refresh
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-08-08 16:55 UTCOSV refresh
- 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-07-27 14:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Related CVEs(same product + same vendor + same CWE)
Same product
7 shownDebian:11:node-js-yaml · Debian:12:node-js-yaml · npm:js-yaml
Same vendor
10 shownredhat:RHSA-2026:15979 · redhat:RHSA-2026:56431 · redhat:RHSA-2026:26411
Frequently asked(5)
What is CVE-2025-64718?
When was the CVE record for CVE-2025-64718 published?
Is CVE-2025-64718 actively exploited?
What is the CVSS score of CVE-2025-64718?
How do I remediate CVE-2025-64718?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-64718
Is Your Infrastructure Affected by CVE-2025-64718?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.