CVE-2026-95354 is a use-after-free vulnerability in the Verifier component of Google Chrome before version 154.0.8037.57. A remote attacker who has already compromised the renderer process can use crafted network traffic to potentially 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 use-after-free vulnerability in Google Chrome's Verifier potentially enables sandbox escape and arbitrary code execution through crafted network traffic, provided the attacker has already compromised the renderer process. The referenced Chainguard chromium-lang package is affected. The plugin assigns a CVSS v3 base score of 8.3 (High), while Chromium rates the vulnerability Medium.
A medium-severity use-after-free vulnerability in Google Chrome's Verifier component that could allow an attacker who had already compromised the renderer process to execute arbitrary code outside Chrome's sandbox through crafted network traffic.
Use-after-free vulnerability in Verifier.
Use-after-free vulnerability in Verifier.
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.