CVE-2025-64718

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

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).

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

November 13, 2025

Last Modified

June 17, 2026

References (5)

Vendor Advisories for CVE-2025-64718(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhceph/grafana-rhel9:17775665462026-05-11redhat

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)
PackageVulnerable rangeFixed inDependents
node-js-yaml3.14.1+dfsg+~3.12.6-2 ... 4.2.0+~4.0.9-1 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
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——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
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——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-js-yaml4.1.0+dfsg+~4.0.5-74.1.1+dfsg+~4.0.9-1—
npm(1)
PackageVulnerable rangeFixed inDependents
js-yaml—3.14.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 28× 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 139 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-64718?
CVE-2025-64718 is a medium vulnerability published on November 13, 2025. 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…
When was CVE-2025-64718 disclosed?
CVE-2025-64718 was first published in the National Vulnerability Database on November 13, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-64718 actively exploited?
CVE-2025-64718 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 65.9% of all scored CVEs.
What is the CVSS score of CVE-2025-64718?
CVE-2025-64718 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2025-64718?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-64718, 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-2025-64718

Explore →

Is Your Infrastructure Affected by CVE-2025-64718?

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

Start Free Scan →Browse All CVEs