Zero Radar
← feed
CriticalVulnerabilityCVE-2026-118332updated 31 Oct 2026, 18:00 UTC

Google Chrome browser flaw lets crafted web pages run code

A flaw in Chrome could let a malicious web page run its own code on your computer. Updating Chrome closes the hole.

Fix availableOfficial, 3 sources
SeverityCriticalCVSS 9.6 of 10
Being exploited?UnclearNo reports either way yet
Fix available?YesGoogle Chrome 156.0.8078.73 or later. ChromeOS / ChromeOS Flex 16836.30.0 (Browser 156.0.8078.77) on the Stable channel. Microsoft Edge receives the fix through its Chromium update. · since 28 Oct 2026
How sure is this?Official, 3 sourcesBacked by an official source

How the attack works simplified

  1. 1Attacker builds pageCrafted HTML exploits the Compositing flaw
  2. 2Page is hostedReached via link, email, or ad
  3. 3User opens pageVulnerable Chrome processes the content
  4. 4Code runsAttacker code executes outside the sandbox
  5. ResultCode runs outside browser sandbox

What happened

Improper input validation in Chrome's Compositing component (the part that draws web page content) lets a remote attacker run arbitrary code outside the browser sandbox via a crafted HTML page. The advisory rates it critical (CVSS 9.6); Chromium's own severity rating is High.

Why it is dangerous: Anyone who opens a malicious or compromised web page in an unpatched browser could have code run on their device, outside the sandbox that normally limits browser damage. Chrome users and Chromium-based Edge users are exposed until they update.

Are you affected?

You are affected if you run Google Chrome earlier than 156.0.8078.73, or a Chromium-based browser such as Microsoft Edge that has not yet received the Chromium fix.

Google Chrome prior to 156.0.8078.73; Microsoft Edge (Chromium-based) builds that have not ingested the Chromium fix (exact Edge versions unknown).

What to do

  1. Update Google Chrome to 156.0.8078.73 or later (or ChromeOS to 16836.30.0 or later)
  2. Update Microsoft Edge to the latest version so it includes the Chromium fix
  3. Restart the browser after updating to finish applying the fix

Timeline

  1. 27 Oct 2026, 23:17 UTC
    Publicly disclosed
  2. 28 Oct 2026, 19:45 UTC
    Reported by Google Chrome · Google Chrome
  3. 28 Oct 2026, 20:32 UTC
    Picked up by Zero Radar
  4. 29 Oct 2026, 17:44 UTC
    NVD reported on it · NVD
  5. 31 Oct 2026, 18:00 UTC
    Microsoft MSRC reported on it · Microsoft MSRC

Sources 3 reports, oldest first

Official vendor, government CERT or advisory database

Technical details

ID
CVE-2026-118332
CVSS
9.6 / 10
Disclosed
27 Oct 2026, 23:17 UTC
On Zero Radar
28 Oct 2026, 20:32 UTC (21 h after disclosure)
Last change
31 Oct 2026, 18:00 UTC

The plain-language parts and the attack diagram were written by an AI model (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 browser flaw lets crafted web pages run code · Zero Radar