CVE-2026-106260 is an incorrect authorization vulnerability in Google Chrome DevTools affecting versions before 155.0.8059.39. A remote attacker can use social engineering and a crafted HTML page to disclose cross-origin data. The specific vulnerable function and required user actions are not identified.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An incorrect authorization vulnerability in Google Chrome DevTools permits a remote attacker to leak cross-origin data through a crafted HTML page with social engineering and user interaction. The Nessus advisory identifies affected Chromium packages without a vendor-supplied patch. Chromium rates the issue Low severity; the listed CVSS v3 base score is 4.3 (Medium).
An incorrect authorization vulnerability in Google Chrome DevTools affecting versions before 155.0.8059.39. A remote attacker could use social engineering and a crafted HTML page to leak cross-origin data. Chromium rates its severity as Low.
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.