CVE-2026-11645 · Published 8 Jun 2026
Google Chromium V8
On CISA's KEV list one day after disclosure; 7 public exploits.
Google Chromium V8 out-of-bounds read and write vulnerability that could allow a remote attacker to execute arbitrary code inside a sandbox 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 23 Jun 2026): 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 9 Jun 2026, due 23 Jun 2026
- EPSS, 30-day forecast
- 2.4%, 85th 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 8 Jun 2026 to today
- Disclosed
- KEV+1 d
- First PoC+1 d
1 days from disclosure to the KEV listing
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
- fevar54/CVE-2026-11645-Out-of-bounds-Read-WriteTrust ok 1003 stars
PoC de CVE-2026-11645: lectura/escritura fuera de limites en Chrome V8 (CVSS 8.8).
created 10 Jun 2026
- 0xBlackash/CVE-2026-11645Trust ok 1001 stars
CVE-2026-11645
created 11 Jun 2026
- 0xredash/CVE-2026-11645Trust ok 1001 stars
CVE-2026-11645
created 11 Jun 2026
- adamshaikhma/CVE-2026-116450 stars
Trust ok 85 · 1 flag
- no source (no_source)
created 10 Jun 2026
- dexteon/cve-2026-11645-pocTrust ok 1000 stars
Research notes for cve-2026-11645-poc
created 12 Nov 2026
- emlinhax/CVE-2026-11645-pocTrust ok 1000 stars
homegrown poc for CVE-2026-11645
created 21 Oct 2026
- ashrafzaryouh/CVE-2026-11645Not checked1 stars
CVE-2026-11645
created 11 Jun 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.