Zero Radar
← feed
HighVulnerabilityCVE-2026-113279updated 27 Oct 2026, 03:00 UTC

Google Chrome: memory flaw in Accessibility features can let a malicious web page run code

A specially crafted web page could corrupt memory inside Chrome's accessibility feature, which may let an attacker run code within Chrome's sandbox. Updating Chrome closes this gap.

Fix availableOfficial, 3 sources
SeverityHighCVSS 8.8 of 10
Being exploited?UnclearNo reports either way yet
Fix available?YesChrome 156.0.8078.47 (Linux) and 156.0.8078.47/.48 (Windows/Mac); ChromeOS LTS-150 version 150.0.7871.287. · since 25 Oct 2026
How sure is this?Official, 3 sourcesBacked by an official source

How the attack works simplified

  1. 1Attacker builds pageCrafted HTML page prepared in advance
  2. 2Victim visits pagePage loaded in vulnerable Chrome
  3. 3Memory corruptionFlaw in Accessibility component triggered
  4. 4Code runs in sandboxArbitrary code execution inside sandbox
  5. ResultAttacker runs code inside the browser sandbox

What happened

Memory corruption in the Accessibility component of Google Chrome prior to 156.0.8078.47, triggered by a crafted HTML page, may allow arbitrary code execution inside the sandbox.

Why it is dangerous: Anyone who visits a malicious or compromised web page in an unpatched Chrome browser could be targeted, especially users who have not yet installed the update.

Are you affected?

You are affected if you run Google Chrome prior to 156.0.8078.47 (Windows, Mac, or Linux) or ChromeOS LTS-150 prior to 150.0.7871.287.

Google Chrome (Desktop) prior to 156.0.8078.47 on Windows, Mac and Linux; ChromeOS LTS-150 prior to 150.0.7871.287.

What to do

  1. Update Google Chrome to 156.0.8078.47 or later (Windows, Mac, Linux)
  2. On ChromeOS LTS devices, update to version 150.0.7871.287 or later
  3. Restart the browser after updating to finish applying the fix

Timeline

  1. 20 Oct 2026, 20:09 UTC
    Publicly disclosed
  2. 20 Oct 2026, 20:09 UTC
    Reported by Chrome Releases · Chrome Releases
  3. 20 Oct 2026, 22:19 UTC
    Reported by NVD · NVD
  4. 27 Oct 2026, 03:00 UTC
    Google Chrome reported on it · Google Chrome

Sources 3 reports, oldest first

Official vendor, government CERT or advisory database

Technical details

ID
CVE-2026-113279
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

Google Chrome: memory flaw in Accessibility features can let a malicious web page run code · Zero Radar