Google Chrome: browser flaw in Accessibility lets a crafted web page run code
A specially built web page could make Chrome misuse memory, letting an attacker run code inside the browser's protective sandbox. Updating Chrome closes the hole.
| Severity | HighCVSS 8.8 of 10 |
|---|---|
| Being exploited? | UnclearNo reports either way yet |
| Fix available? | YesChrome 156.0.8078.47 or later (desktop); LTS-150 version 150.0.7871.287 or later (ChromeOS) · since 25 Oct 2026 |
| How sure is this? | Official, 3 sourcesBacked by an official source |
How the attack works simplified
- 1Attacker builds pageCrafted HTML page with malicious payload
- 2Victim opens pageUser visits the page in Chrome
- 3Accessibility bug triggersUse-after-free corrupts memory
- 4Code runs in sandboxAttacker executes arbitrary code
- ResultAttacker runs code inside Chrome's sandbox
What happened
A use-after-free memory bug in Chrome's Accessibility component allows a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page.
Are you affected?
You are affected if you run Google Chrome versions prior to 156.0.8078.47 on Windows, Mac or Linux, or ChromeOS LTS-150 builds prior to 150.0.7871.287.
Google Chrome (desktop) prior to 156.0.8078.47 (Linux) / 156.0.8078.47/.48 (Windows/Mac); Chrome LTS-150 for ChromeOS prior to 150.0.7871.287
What to do
- Update Google Chrome to version 156.0.8078.47 or later (Windows, Mac, Linux)
- On ChromeOS LTS devices, update to version 150.0.7871.287 or later
- Restart the browser after updating so the fix takes effect
Timeline
- 20 Oct 2026, 20:09 UTCPublicly disclosed
- 20 Oct 2026, 20:09 UTCReported by Chrome Releases · Chrome Releases
- 20 Oct 2026, 22:19 UTCReported by NVD · NVD
- 27 Oct 2026, 03:00 UTCGoogle Chrome reported on it · Google Chrome
Sources 3 reports, oldest first
Official vendor, government CERT or advisory database
- Stable Channel Update for DesktopChrome Releases · 20 Oct 2026, 20:09 UTC
- NVD20 Oct 2026, 22:19 UTC
- Long Term Support Channel Update for ChromeOSGoogle Chrome · 27 Oct 2026, 02:10 UTC
Technical details
- ID
- CVE-2026-113271
- CVSS
- 8.8 / 10
- EPSS
- 0.5% chance of exploitation within 30 days
- Disclosed
- 20 Oct 2026, 20:09 UTC
- On Zero Radar
- before the radar started
- Last change
- 27 Oct 2026, 03:00 UTC
The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works