Google Chrome: Memory corruption in Accessibility
Summary
Memory corruption in the Accessibility component of Google Chrome before 156.0.8078.47 may allow a remote attacker to potentially execute arbitrary code inside the browser sandbox. The attacker needs a user to open a crafted HTML page, but no privileges are required. The stated impact is code execution inside the sandbox, not a sandbox escape, and a complete attack chain is not confirmed.
Affected
- Google Chrome (desktop) before 156.0.8078.47 per the CVE description
- VulDB lists the affected range as up to 155.0.8059.84; the range shown on one mirror page is malformed and unreliable
- Chromium-based browsers and Linux distribution packages may inherit the fix (unverified)
Fixed in
- Chrome 156.0.8078.47 (Linux); 156.0.8078.47/.48 (Windows and Mac), per secondary reports of the 20 October 2026 Stable release
- Later Stable builds exist; the current latest build could not be confirmed from a primary source
Workaround
Unknown. No vendor workaround identified. The remedy is updating Chrome.
Exploitation
- No evidence of in-the-wild exploitation found
- Not listed in CISA KEV (per one mirror source)
- CISA SSVC: Exploitation none, Automatable no
- No public proof of concept identified; this does not prove that none exists
Our recommendation
- Update Chrome to the newest Stable build from the Chrome Releases blog on all Windows, Mac and Linux systems
- Restart the browser after updating, because running processes keep the old code
- Check managed and portable installs, and Chromium-based browsers such as Microsoft Edge, for the fix
- Check Linux systems that use distribution Chromium packages
- Monitor the CISA KEV catalogue and the Chrome Releases blog for exploitation reports
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Chrome Releases: Stable Channel Update for Desktop chromereleases.googleblog.com
- Chromium issue tracker entry issues.chromium.org
- VulDB entry (affected range and score) vuldb.com
- Strix CVE mirror www.strix.ai
- Vulners CVE listing vulners.com
- CyberSecurityNews: Chrome 156 security update cybersecuritynews.com
- GBHackers: Google Chrome 156 fixes gbhackers.com
- Penligent: Chrome 156 security update www.penligent.ai
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 12:24.
Original description (NVD)
Memory corruption in Accessibility in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.