Loading vulnerability…
CVE-2026-12009 is an insufficient input-validation vulnerability in the Accessibility component of Google Chrome on macOS before version 149.0.7827.115. A remote attacker who has already compromised the renderer process could potentially exploit the flaw through a crafted HTML page to escape the renderer sandbox. The specific vulnerable function and validation failure are not identified.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An input-validation vulnerability in Chrome's Accessibility component that potentially enables sandbox escape through a crafted HTML page after an attacker has compromised the renderer process. Chromium rates the flaw Critical; the plugin lists a CVSS v3 base score of 8.3 and High severity.
A critical insufficient validation of untrusted input vulnerability in the Chrome Accessibility component that could be exploited via a specially crafted web page and contribute to arbitrary code execution or compromise.
A critical insufficient input validation vulnerability in Chrome Accessibility features that could potentially allow attackers to execute arbitrary code or gain control over affected systems.
A critical insufficient validation of untrusted input vulnerability in Chrome Accessibility.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.