FalehSec Exploited-vulnerability triage · joined from CISA KEV, NVD CVSS and EPSS

CVE-2025-5419

Google · Chromium V8 · Google Chromium V8 Out-of-Bounds Read and Write Vulnerability

Verdict
Patch first · actively exploited, reachable from the internet without credentials, and in the top 10% of CVEs by near-term exploitation probability

Added to CISA KEV 2025-06-05 · exploited in the wild for 520 days

How a test catches it

Test
Submit the declared length boundary, one past it, and an order of magnitude past it, to every parameter that reaches a fixed or computed buffer, and watch for a crash, a reset, or a changed response length.
Passes when
The input is bounded before it reaches the buffer. A crash, a reset, or a silent change in response length under an oversized value is the finding, and confirming it needs no exploitation - the crash is the evidence.
What an attacker can reach How likely Time What CISA says to do Sources All 566

What an attacker can reach

CVSS 8.8 HIGH. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.

Attack vectornetworkreachable over the network, with no local access needed
Privileges requirednoneneeds no credentials at all
User interactionrequiredneeds a user to click, load or submit something first
Base vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
WeaknessCWE-125

This describes the vulnerability. It says nothing about whether your systems run it.

How likely

EPSS puts the probability of exploitation in the next 30 days at 0.0749, which places it in the top 10% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.

EPSS probability0.0749
Percentile0.945 — top 10%

Time

Added to KEV2025-06-05
Days exploited520
Federal remediation duenot set
Ransomware useno known ransomware campaign use

What CISA says to do

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

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)

Sources

This page describes the bug, not your estate. It cannot tell you whether you run it, or whether your own systems carry the same class of flaw. That question is what an assessment answers.

Web application penetration testing · API security testing · every service