Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Low

Site isolation bypass in Google Chrome Extensions

IdentifiersCVE-2026-12017CWE-20· Improper Input Validation

CVE-2026-12017 is a high-severity vulnerability in the Extensions component of Google Chrome caused by insufficient validation of untrusted input / inappropriate implementation. In Google Chrome prior to 149.0.7827.115, a remote attacker who had already compromised the renderer process could use a crafted HTML page to bypass site isolation. The available advisories do not disclose the specific vulnerable function or code path, but the issue is explicitly described as residing in Extensions and enabling a renderer-compromise-to-site-isolation-bypass chain.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker who has already achieved renderer-process compromise to bypass Chrome site isolation protections. This can weaken Chrome's process-based security boundaries and potentially enable access to data or content that should remain isolated across sites or origins. Vendor and downstream advisories for Chromium broadly note possible consequences including information disclosure and other security impact, but the specific documented impact for this CVE is site isolation bypass rather than standalone initial code execution.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround or temporary mitigation is provided in the available advisories. The practical mitigation is to apply the relevant browser security update promptly. Reducing exposure to renderer compromise through general browser hardening may reduce exploitability, but no CVE-specific mitigation short of patching is documented in the provided content.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 149.0.7827.115 or later. For Chromium on Debian, apply the vendor security updates by upgrading to 149.0.7827.114-1~deb12u1 on Debian oldstable (bookworm) or 149.0.7827.114-1~deb13u1 on Debian stable (trixie). For Microsoft Edge (Chromium-based), update to version 149.0.4022.69, which ingests the Chromium fix.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.