CVE-2026-106293 is a type-confusion vulnerability in the ANGLE component of Google Chrome before version 155.0.8059.39. A remote attacker who has already compromised the renderer process can use a crafted HTML page to potentially execute arbitrary code outside the Chrome sandbox. The specific vulnerable function is 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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity type-confusion vulnerability in Chrome's ANGLE component that can allow sandbox escape and arbitrary code execution through crafted HTML after the renderer process has been compromised. The plugin identifies affected Linux/Unix packages for which no vendor patch is available. The reported CVSS v3 base score is 8.3.
A high-severity type confusion vulnerability in Chrome's ANGLE component could allow a remote attacker to escape the sandbox and execute arbitrary code through a crafted HTML page. Exploitation requires an already-compromised renderer process. The affected versions are Google Chrome versions prior to 155.0.8059.39.
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.