Loading vulnerability…
CVE-2026-95342 is a V8 cross-security-token capability disclosure in stack-trace CallSite handling. V8 could capture stack frames while executing under one security token and subsequently expose CallSite objects to an Error.prepareStackTrace callback executing under a different security token. CallSite.prototype.getFunction() could return a private function object created in the trusted realm without validating that the caller's native context had an equivalent security token. An untrusted realm could then invoke the leaked function and access data or capabilities available to the trusted realm. Related CallSite getters could also expose incompatible cross-token values. The issue affected V8-based products, including Chrome, and was addressed in Chrome 154.0.8037.57/.58.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.