CVE-2026-70609 is an improper input-sanitization vulnerability in Electron's DevTools handling. In Electron releases before 39.8.7, 40.9.0, 41.2.0, and 42.0.0-beta.1, the mode option supplied to webContents.openDevTools() was used by the DevTools frontend without sanitization. An attacker able to control this value can inject and execute JavaScript in the DevTools context. The issue can be reached when untrusted input is passed to the mode argument or when untrusted content in an embedded webview can invoke openDevTools().
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.
A vulnerability in Electron where an unsanitized dock-state parameter could allow JavaScript injection into Electron DevTools under specific advisory conditions.
An Electron input-sanitization flaw in webContents.openDevTools() that can permit attacker-controlled script execution in the DevTools context. In unsandboxed configurations, this context has Node.js access. Exploitation requires an attacker to influence the mode argument or cause untrusted embedded webview content to invoke openDevTools().
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.