CVE-2025-5419: Google Chromium V8 Out-of-Bounds Read and Write Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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)

Description quoted from the CVE record (assigned by Chrome, published 2025-06-02).

Weakness: CWE-125 Out-of-bounds Read; CWE-787 Out-of-bounds Write

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.

On CISA KEV since
2025-06-05
US federal deadline
2025-06-26
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2025-06341, BDU:2025-06391, CNNVD-202506-135, CNVD-2025-11252, EUVD-2025-16695, GHSA-x828-wp24-7h9m

VEDAS cluster: VEDAS:FURYDUSK

Exploit Observer links 9 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (9)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (5)

Vulnerability databases and vendor advisories (14)

Catalogue entries, not exploit evidence.

275 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.075
some chance of attack soon
VEDAS
0.975
strong exploit evidence
On CISA KEV
Yes, since 2025-06-05
Detection rule
None yet
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1CVE-2025-5419 EPSS over time2025-062026-11-01
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.9CVE-2025-5419 VEDAS over time2025-062026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Google Chromefrom 137.0.7151.68 before 137.0.7151.68Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: google chrome, google_inc google_chrome, ооо_«ред_софт» ред_ос.

How to fix it

Fixed versions stated in the CVE record: 137.0.7151.68.

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

Vendor guidance:

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

Advisories on this CVE

References

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.