CVE-2026-11645
chromium-browser: Out of bounds memory access in V8
Exploitation confirmed. First attested on 2026-06-09 by CISA-ADP, CISA KEV, GCVE · kevintel.
- Published2026-06-09
- Fixed in149.0.7827.103
- WeaknessCWE-125 · CWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Out of bounds read and write in V8 in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Timeline
dates in UTCObserved activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-11645?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-11645?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 149.0 | < 149.0.7827.103 | 149.0.7827.103 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
- CVE-2026-11645 Red Hat Product Security
chromium-browser: Out of bounds memory access in V8
Fix
- Update Google chrome to 149.0.7827.103
- CISA’s 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.due 2026-06-23
Advisories and patches
- chromereleases.googleblog.comRelease Notes · Vendor Advisory
Detection
read 2026-10-23 19:24 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 4 repositories, unverifiedfevar54/CVE-2026-11645-Out-of-bounds-Read-Writeadamshaikhma/CVE-2026-116450xBlackash/CVE-2026-11645emlinhax/CVE-2026-11645-poc PoC-in-GitHub
CISA Known Exploited Vulnerability
- Date Added
- 2026-06-09
- Patch Due Date
- 2026-06-23
- Ransomware Use
- Unknown
- 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.
Sources
- NVDCVE recordread 2026-10-23
- CISA KEVKEV entry2026-06-09
- GCVEexploitation2026-06-09
- CISA-ADPSSVC decisionactive2026-06-09
- OpenCVESSVC decisionactive—
- CISA-ADPCVSS 3.18.82026-06-09
- CISA-ADPweakness (CWE)CWE-125, CWE-7872026-06-09
- FIRST EPSSEPSS score2.4 %2026-10-23
- PoC-in-GitHubproof of concept4read 2026-10-23
- Microsoft MSRCadvisory—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2026-06-09
- Last Modified
- 2026-07-23
- NVD status
- Analyzed
- MSRC Title
- Chromium: CVE-2026-11645 Out of bounds memory access in V8
Frequently asked questions
What is CVE-2026-11645?
Is CVE-2026-11645 actively exploited?
What is the CVSS score for CVE-2026-11645?
Running chromium-browser? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.