CVE-2025-5419 · Published 2 Jun 2025
Google Chromium V8
On CISA's KEV list 3 days after disclosure; 7 public exploits.
Google Chromium V8 contains an out-of-bounds read and write vulnerability that could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
CISA required action (federal due date 26 Jun 2025): Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Signals
- KEV, exploited in the wild
- yes, added 5 Jun 2025, due 26 Jun 2025
- EPSS, 30-day forecast
- 7.6%, 95th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 2 Jun 2025 to today
- Disclosed
- KEV+3 d
- First PoC+9 d
9 days from the KEV listing to the first proof of concept
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 0 dispatches
No dispatch on our wire has named this CVE yet.
Public exploit code 7 known · links only
GitHub PoCs 7Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars7
- mistymntncop/CVE-2025-5419Trust ok 10095 stars
created 25 Aug 2025
- bjrjk/CVE-2025-5419Trust ok 10030 stars
An uninitialized read vulnerability by incorrect Turboshaft Store-Store Elimination in V8.
created 29 Jan 2026
- itsShotgun/chrome_v8_cve_checkerTrust ok 1002 stars
Checks if your Chrome version is vulnerable to CVE-2025-5419, from the browser
created 14 Jun 2025
- dexteon/cve-2025-5419-pocTrust ok 1000 stars
Research notes for cve-2025-5419-poc
created 12 Nov 2026
- riemannj/CVE-2025-5419Trust ok 1000 stars
Dissecting CVEin Chrome
created 13 Aug 2025
- pavan3478/CVE-2025-5419Not checked
first seen by skopnix 18 Oct 2026
- somprasong-tukman/CVE-2025-5419Not checked
first seen by skopnix 18 Oct 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.