CVE-2026-12457: Chrome Site Isolation Bypass via Extension Flaw

Technical summary

The vulnerability stems from an inappropriate implementation in Chrome's extension handling mechanism that fails to properly enforce site isolation boundaries. An attacker with renderer process compromise can craft a malicious HTML page that, when processed by the browser, bypasses the site isolation restriction (CWE-693: Improper Neutralization of Special Elements used in an SQL Command). This allows the attacker to read and potentially modify content across site boundaries within the renderer's authority. The issue affects Chrome on Windows, macOS, and Linux systems.

Business impact

For most organizations, the direct risk is limited because the attack requires a prior renderer compromise—typically delivered through a separate vulnerability or social engineering. However, the ability to bypass site isolation amplifies the impact of any renderer exploit, turning a single-site compromise into a multi-site data theft vector. For users who frequent untrusted websites or receive targeted attacks, this could enable credential theft, session hijacking, or exfiltration of sensitive information from other open tabs. Organizations with strict extension policies may face increased pressure from users running unapproved extensions that could exploit this flaw.

Affected systems

Google Chrome prior to version 149.0.7827.155 on all platforms (Windows, macOS, Linux). The vulnerability is platform-agnostic and affects the core Chrome rendering engine. Users of Chromium-based browsers (Edge, Brave, Opera, etc.) should verify whether they have backported this fix from the upstream Chromium project, though the source data lists only the official Chrome releases.

Exploitability

Exploitability is moderate. While the CVSS score of 4.2 reflects the attack complexity—requiring prior renderer compromise—the underlying flaw itself is not difficult to trigger once that precondition is met. The attacker must deliver both a renderer exploit and a crafted HTML page, making this a chained attack rather than a standalone one. No public exploit code is known to exist at the time of publication. The requirement for user interaction (opening a malicious page) is subsumed within the renderer compromise scenario.

Remediation

Update Google Chrome to version 149.0.7827.155 or later. Chrome's automatic update mechanism will deploy this patch to most users within days of release; however, organizations should verify deployment in managed environments. Users who have disabled auto-updates must manually trigger an update check. For Chromium-based browsers, check the vendor's security advisory for patch availability and timelines.

Patch guidance

Deploy Chrome 149.0.7827.155 or later across all endpoints. For enterprise environments using Chrome Enterprise or managed devices: verify that automatic updates are enabled and monitor Chrome version distribution to confirm patch coverage within 7–14 days of release. For users on restricted networks, download the installer directly from Google's official channels and stage it through your software distribution system. No workarounds exist; patching is the only mitigation. Test the patch in a non-production environment first if your organization customizes Chrome policies or relies on specific extensions.

Detection guidance

Monitor browser version strings in logs and telemetry for Chrome versions below 149.0.7827.155. If you have visibility into extension behavior, watch for unusual cross-site requests or data reads that violate expected extension permissions. Behavioral detection is difficult without deep browser instrumentation; however, successful exploitation would manifest as unexpected data exfiltration from authenticated sessions on unrelated websites. Ensure logging of extension installation and modification events is enabled and reviewed regularly.

Why prioritize this

Although the CVSS score is medium (4.2), the vulnerability warrants prompt attention because it directly undermines Chrome's most important sandbox boundary. Site isolation is the last line of defense against renderer exploits. Any flaw that weakens it increases the blast radius of other Chrome vulnerabilities. Prioritize patching for users who browse untrusted content, receive targeted phishing, or handle sensitive credentials in multiple browser tabs simultaneously. Delayed patching combined with a separate renderer exploit in the wild could create significant data exfiltration risk.

Risk score, explained

The CVSS 3.1 score of 4.2 (MEDIUM severity) reflects the attack's prerequisites: network access and the need for prior renderer process compromise (AC:H), combined with limited impact scope (confidentiality and integrity only, no availability impact). The score accurately captures that this is not a critical vulnerability on its own. However, the contextual risk is higher when considered in combination with other Chrome exploits or in high-value attack scenarios where an attacker is already investing effort to compromise the renderer.

Frequently asked questions