CVE-2025-5419

Exp

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)

Published: 2025-06-03 Last update: 2025-10-24 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-5419 is rated Critical Active Threat (91.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 3.83%). CISA KEV confirms active exploitation (added 2025-06-05) affecting Google / Chromium V8. a weakness (CWE-125) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2025-5419

Name: Google Chromium V8 Out-of-Bounds Read and Write Vulnerability · CISA KEV detail

Exploit added: 2025-06-05

Action due: 2025-06-26

Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Exploit prediction scoring system (EPSS) score for CVE-2025-5419

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-26 3.50% 3.83% +0.32%
2 2026-05-02 3.26% 3.50% +0.25%
3 2026-03-29 — 3.26% —

Full EPSS history (64 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-5419

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-5419

OS Trackers for CVE-2025-5419

vendor priority summary link
alpine — CVE-2025-5419: 1 source package rows (qt6-qtwebengine); 1 state rows across 1 repos (3.22-community); fixed 1, open 0. https://security.alpinelinux.org/vuln/CVE-2025-5419
debian end-of-life CVE-2025-5419 end-of-life priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-5419
ubuntu medium CVE-2025-5419 medium priority: Ubuntu including 1 source packages (chromium-browser), 5 status rows across 5 suites (jammy, noble, oracular, plucky, upstream): not-affected 4, released 1. https://ubuntu.com/security/CVE-2025-5419

Affected software / configurations for CVE-2025-5419

Vendor Product Version Raw CPE
google chrome < 137.0.7151.68 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
microsoft edge_chromium < 137.0.3296.62 cpe:2.3:a:microsoft:edge_chromium:*:*:*:*:*:*:*:*

References for CVE-2025-5419

cvelogic Threat Intelligence