Google Chrome: Use-after-free in Accessibility enables code execution in sandbox
Summary
A use-after-free flaw in the Accessibility component of Google Chrome prior to 156.0.8078.47 allows a remote attacker to execute arbitrary code inside the browser sandbox. The attack requires a victim to visit a crafted HTML page, so phishing or a compromised website is the realistic path. Code execution inside the sandbox is not a full compromise on its own, but it is a foothold that may be combined with a sandbox escape. Chromium rates the issue Medium and CVSS 3.1 rates it 8.8 (High).
Affected
- Google Chrome prior to 156.0.8078.47 (CNA range)
- Chromium-based browsers that have not yet ingested the fix, such as Microsoft Edge prior to 156.0.4314.42 (per HKCERT)
- Linux distributions: check your distribution's advisory, as packaging differs (Ubuntu lists its chromium-browser snap as not affected)
Fixed in
- Google Chrome 156.0.8078.47 or later (Linux and Android)
- Google Chrome 156.0.8078.47 or 156.0.8078.48 or later (Windows and macOS, per secondary reports)
- Microsoft Edge 156.0.4314.42 or later
- The Google release notice could not be retrieved during research; verify the exact build numbers against it.
Workaround
- None documented. Mitigation is to update Chrome and restart the browser, because an old browser process may keep running after an update prompt.
Exploitation
- No evidence of exploitation in the wild found at the time of research.
- No public proof of concept found.
- No CISA KEV entry found in research; check the KEV catalogue directly.
- CISA SSVC assessment: exploitation none, not automatable, total technical impact.
Our recommendation
- Update Google Chrome to the fixed build on all endpoints and restart the browser.
- Verify the installed version on each device rather than assuming the automatic update has applied, especially on managed fleets.
- Update Chromium-based browsers (Edge, Brave, Opera and similar) and check Linux distribution advisories.
- Raise user awareness about links and attachments from untrusted sources.
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
- Vulners: CVE-2026-113319 (CVELIST) vulners.com
- Ubuntu security: CVE-2026-113319 ubuntu.com
- OffSeq Radar: CVE-2026-113319 radar.offseq.com
- HKCERT: Microsoft Edge multiple vulnerabilities www.hkcert.org
- TechGeeks: Google Chrome 156 stable security notice www.techgeeks.org
- 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, 11:56.
Original description (NVD)
Use after free in Accessibility in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
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.