Loading vulnerability…
CVE-2026-95300 is an authorization flaw in Chromium DevTools remote frontend handling. Remotely loaded DevTools frontends shared the privileged DevTools origin with local frontends and could invoke C++ embedder bindings without adequate local-frontend authorization. A malicious remote-debugging target could induce a developer to load a legacy remote DevTools frontend containing a known XSS flaw. JavaScript executing through that flaw could use privileged DevTools operations to alter browser feature preferences, request a browser restart, modify profile-wide DevTools preferences, or open arbitrary web tabs. The fix restricts privileged DevTools APIs to local frontends through local-frontend authorization checks.
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.