Loading vulnerability…
CVE-2026-87512 is a high-severity use-after-free vulnerability in the ANGLE graphics translation component of Google Chrome on Windows before version 153.0.8010.36. A remote attacker can trigger the memory-safety flaw through a crafted HTML page, enabling arbitrary code execution outside Chrome's browser 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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity vulnerability in Chrome's ANGLE component addressed by Chrome 153.
A high-severity vulnerability in Chrome's ANGLE component fixed in Chrome 153.
A high-severity use-after-free vulnerability in ANGLE affecting Google Chrome on Windows before version 153.0.8010.36. A remote attacker could use a crafted HTML page to execute arbitrary code outside Chrome's sandbox.
A network-reachable vulnerability requiring user interaction, with no privileges required, that can result in high impact to confidentiality, integrity, and availability. The content identifies affected Debian Linux versions but does not name the vulnerable component.
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.