Skip to main content
Mallory
High

Sandbox Escape in Google Chrome Accessibility on Mac

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

CVE-2026-12009 is a critical insufficient validation of untrusted input vulnerability in the Accessibility component of Google Chrome on macOS prior to version 149.0.7827.115. According to the provided content, a remote attacker who has already compromised the renderer process can leverage a crafted HTML page to trigger the flaw and potentially escape Chrome’s sandbox. The issue is described by Google/Chromium as insufficient validation of untrusted input in Accessibility, but no more specific vulnerable function or code path is provided in the available material.

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 could allow an attacker who already achieved renderer-process compromise to break out of the Chrome sandbox on macOS. This can enable execution of actions outside the renderer’s sandbox restrictions and may facilitate further code execution, broader access to the host system, or eventual full system compromise depending on post-escape capabilities and local conditions.

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 updating immediately, restarting the browser to complete deployment, and limiting opportunities for renderer compromise by restricting access to untrusted web content until patched. Because exploitation requires prior renderer compromise, broader browser hardening and rapid patching of related Chrome vulnerabilities also reduce risk.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome on macOS to version 149.0.7827.115 or later. For Chromium on Debian, apply the vendor security updates referenced in the content, including 149.0.7827.114-1~deb12u1 for Debian oldstable (bookworm) or 149.0.7827.114-1~deb13u1 for Debian stable (trixie), as applicable. More generally, deploy the Chrome/Chromium release containing the fix for CVE-2026-12009 across affected systems promptly.
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.

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 activity2

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