CVE-2026-11282: Google Chrome · Policy Bypass
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 9.6 Critical : upgrade to 149.0.7827.53 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% 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:L/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 Chrome and google/chrome to 149.0.7827.53.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
Googlegoogle/chromepkg:deb/google/chromeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor advisory link should be monitored for updates regarding patch availability. Since the affected version is prior to 149.0.7827.53, updating to version 149.0.7827.53 or later is recommended once confirmed by the vendor.
Description
A policy enforcement bypass vulnerability exists in the sandbox of Google Chrome on Linux versions prior to 149.0.7827.53. This flaw could allow a remote attacker to escape the sandbox by delivering a crafted HTML page. The vulnerability is rated critical with a high CVSS score of 9.6. No known exploits in the wild have been reported. A vendor advisory is available but does not explicitly confirm patch status or remediation details.