CVE-2026-11281: Google Chrome · Integer Overflow
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 5.0 Medium : upgrade to 149.0.7827.53 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% 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:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:NExploitation 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
Users should update Google Chrome on Windows to version 149.0.7827.53 or later to remediate this vulnerability. The vendor advisory confirms that this update fixes the issue. No additional mitigation actions are specified or required.
Description
An integer overflow vulnerability exists in the Chromoting component of Google Chrome on Windows versions prior to 149.0.7827.53. This flaw allows a local attacker to potentially access sensitive information from process memory by leveraging a crafted ETW event. The vulnerability has been assigned a medium severity rating with a CVSS score of 5. A fix is available in version 149.0.7827.53.