CVE-2025-5419

CRITICALPre-NVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-06-05), indicating real-world exploitation has been confirmed by US federal agencies. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa-adp, cisa_kev, epss, ghsa
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 8%CVSS: 8.8Exploit: cisa kev · ssvc active · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Out of bounds read and write in V8 in Google Chrome prior to 137.0.7151.68 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CVSS v3
8.8
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/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
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
8%
EPSS %ILE
94%
KEV
⚠ Exploited

Published

June 3, 2025

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Jun 1, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft, cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-5419
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-5419
generic🔴 Active Exploitation

Chromium

https://issues.chromium.org/issues/420636529
generic🔴 Active Exploitation

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop.html

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 137.0.7151.55-3~deb12u1 (220 versions)137.0.7151.68-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium—137.0.7151.68-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium—137.0.7151.68-1—

Weakness Classification(2)

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

All Vendor Advisories

(1)

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 107× in last 7d / 446× 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 1,689 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCbjrjk/CVE-2025-5419
    First seen Jan 29, 2026

    An uninitialized read vulnerability by incorrect Turboshaft Store-Store Elimination in V8.

    Open source ↗
  • GitHub PoCmistymntncop/CVE-2025-5419
    First seen Aug 25, 2025
    Open source ↗
  • GitHub PoCitsShotgun/chrome_v8_cve_checker
    First seen Jun 14, 2025

    Checks if your Chrome version is vulnerable to CVE-2025-5419, from the browser

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2025-5419?
CVE-2025-5419 is a critical vulnerability published on June 3, 2025. Out of bounds read and write in V8 in Google Chrome prior to 137.0.7151.68 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
When was CVE-2025-5419 disclosed?
CVE-2025-5419 was first published in the National Vulnerability Database on June 3, 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-5419 actively exploited?
Yes. CISA added CVE-2025-5419 to the Known Exploited Vulnerabilities catalog on June 5, 2025, affecting Google Chromium V8. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2025-5419?
CVE-2025-5419 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2025-5419?
CVE-2025-5419 affects Google Chromium V8. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2025-5419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-5419, 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-5419

Explore →

Is Your Infrastructure Affected by CVE-2025-5419?

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

Book a Demo →Browse All CVEs