Loading vulnerability…
CVE-2026-12027 is a high-severity insufficient policy enforcement vulnerability in the Headless component of Google Chrome prior to 149.0.7827.115. The flaw is described as an inappropriate implementation / insufficient policy enforcement issue that allows a remote attacker, after first compromising the renderer process, to potentially escape Chrome's sandbox by using a crafted HTML page. The vulnerability affects the security boundary intended to confine renderer compromise and prevent code or actions from reaching a more privileged execution context outside the renderer sandbox.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An insufficient policy enforcement vulnerability in Google Chrome Headless that can allow security restriction bypass via a crafted HTML page.
A high-severity insufficient policy enforcement vulnerability in Chrome Headless.
A high-severity insufficient policy enforcement vulnerability in Chrome Headless.
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.