CVE-2026-3063 is a high-severity inappropriate implementation flaw in DevTools in Google Chrome prior to 145.0.7632.116. The weakness allows a malicious browser extension, once installed by a user, to inject script or HTML into a privileged browser page through DevTools. The issue is rooted in improper handling of trust and boundary separation between extension-controlled content and privileged browser contexts exposed through developer tooling. Successful exploitation can break expected isolation guarantees around privileged pages and enable attacker-controlled content to execute or render where it should not be permitted.
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.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown (listed as a trending CVE affecting Google Chrome).
Unknown (listed as a trending CVE affecting Google Chrome; no technical details provided in the content).
A high-severity Google Chrome DevTools implementation flaw that allows malicious extensions to inject scripts into privileged pages, increasing risk for users with untrusted extensions installed.
High-severity inappropriate implementation flaw in Chrome DevTools that could, under certain conditions, enable cross-origin data exposure, privilege misuse, or bypass of browser security controls.
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.