CVE-2026-4439: Google Chrome · Out of Bounds Memory Access
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 146.0.7680.153 soon.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 146.0.7680.153
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 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 31 Oct 2026.
What to do
Upgrade Google Chrome to 146.0.7680.153.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-4439, organizations should prioritize updating Google Chrome on all Android devices to version 146.0.7680.153 or later as soon as possible. Since no direct patch links were provided, users should rely on official Google Chrome update channels or managed enterprise update systems. Beyond patching, organizations can implement the following specific measures: 1) Disable or restrict WebGL usage in Chrome via enterprise policies or browser settings to reduce exposure to WebGL-based attacks. 2) Employ mobile device management (MDM) solutions to enforce browser version compliance and restrict installation of unapproved applications. 3) Educate users about the risks of visiting untrusted websites and the importance of avoiding suspicious links to reduce the likelihood of triggering the exploit. 4) Enable Chrome’s built-in security features such as site isolation and sandboxing enhancements to limit the impact of potential exploits. 5) Monitor network traffic and endpoint logs for unusual activity indicative of exploitation attempts or sandbox escapes. 6) Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) tools capable of detecting memory corruption exploits. These targeted mitigations complement patching and help reduce the attack surface and potential damage.
Description
Out of bounds memory access in WebGL in Google Chrome on Android prior to 146.0.7680.153 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)