CVE-2026-95335 is a use-after-free vulnerability in the HID component of Google Chrome versions earlier than 154.0.8037.57. A remote attacker who has already compromised the renderer process could potentially exploit the flaw through a crafted HTML page to execute arbitrary code outside the 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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity use-after-free vulnerability in Google Chrome's HID component could enable sandbox escape and arbitrary code execution through a crafted HTML page, provided the attacker has already compromised the renderer process. The advisory identifies affected Chainguard chromium-lang packages and recommends updating to version 154.0.8037.92-r0 or later. The CVSS v3 base score is 8.3.
A high-severity use-after-free vulnerability in Google Chrome's HID component that could allow an attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox using a crafted HTML page.
Use-after-free vulnerability in HID.
Use-after-free vulnerability in HID.
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.