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 for Android Passwords

IdentifiersCVE-2026-12032CWE-693

CVE-2026-12032 is a high-severity vulnerability in the Passwords component of Google Chrome on Android prior to version 149.0.7827.115. The issue is described as an inappropriate implementation that allows a remote attacker, after first compromising the renderer process, to bypass Chrome site isolation protections using a crafted HTML page. Based on the available information, the flaw affects the enforcement of security boundaries intended to isolate content from different sites, weakening Chrome's process isolation model on Android.

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 already has renderer-process compromise to bypass site isolation on Chrome for Android. This can weaken cross-site security boundaries and may enable access to data or application state that should remain isolated between sites. The provided advisories do not specify the full downstream consequences beyond the site isolation bypass, but such a bypass can materially increase the impact of a renderer compromise.

Mitigation

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

No specific workaround or temporary mitigation is provided in the supplied content. Practical mitigation is to reduce exposure by promptly updating Chrome on Android to a fixed version. Because exploitation requires prior renderer compromise, maintaining current browser versions and minimizing exposure to malicious web content may reduce risk, but patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome on Android to version 149.0.7827.115 or later. For downstream Chromium consumers, apply the corresponding vendor security updates that include the fix for CVE-2026-12032.
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.