CVE-2026-11040: Google Chrome · Use After Free
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 149.0.7827.53 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 149.0.7827.53
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Google Chrome to 149.0.7827.53.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
A fix is available as indicated by the vendor's stable channel update advisory. Users and administrators should update Google Chrome to version 149.0.7827.53 or later to remediate this vulnerability. Patch status is confirmed by the vendor advisory linked to the stable channel update. No additional mitigation steps are specified by the vendor.
Description
CVE-2026-11040 is a use-after-free vulnerability in the ANGLE component of Google Chrome prior to version 149.0.7827.53. This flaw could allow a remote attacker who has already compromised the renderer process to potentially escape the browser sandbox by using a specially crafted HTML page. The vulnerability carries a high severity rating with a CVSS score of 8.3. There are no known exploits in the wild at this time. Google has published an advisory linked to a stable channel update addressing this issue.