Vulnerability in electron (CVE-2026-70608)
Summary
Vulnerability in electron (CVE-2026-70608). Risk of unauthorized operations or information disclosure. Exploitable via setWindowOpenHandler. Mitigation: upgrade to 39.8.10 or later.
Original description
The description as published by the source.
Impact
A sandboxed iframe without the allow-popups keyword could still open a new window (or trigger setWindowOpenHandler) with no user interaction, because new-window navigations taking the OpenURL path did not apply the iframe sandbox popup restriction.
Apps that embed untrusted content in sandboxed iframes and rely on the absence of allow-popups to prevent window creation are affected. Apps that deny window creation in setWindowOpenHandler, or that do not embed untrusted content in sandboxed iframes, are not affected.
Workarounds
Return { action: 'deny' } from setWindowOpenHandler for any content you do not trust, rather than relying on the iframe sandbox alone.
Fixed Versions
42.0.141.10.339.8.10
For more information
If you have any questions or comments about this advisory, email Electron at security@electronjs.org
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-70608 has been found in electron.
Attackers can target a specific entry point like setWindowOpenHandler over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.2/10.
What to do: upgrade electron to 39.8.10 or later.
If unsure, ask your IT team or search "electron CVE-2026-70608" on the vendor's site.
CVE-2026-70608 (electron) — CWE-693 / CVSS v3 7.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: setWindowOpenHandler
Patched: 39.8.10 — apply immediately
Workaround: Return { action: 'deny' } from setWindowOpenHandler for any content you do not trust, rather than relying on the iframe sandbox alone.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-693) exists in electron. Attackers reach the vulnerable code path via setWindowOpenHandler without authentication.
Check the vendor advisory for the affected versions of electron. Attack surface: setWindowOpenHandler.
Severity: High (CVSS 7.2/10). Risk of unauthorized operations or information disclosure.
Update to 39.8.10.
Workaround: Return { action: 'deny' } from setWindowOpenHandler for any content you do not trust, rather than relying on the iframe sandbox alone.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'electron' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'electron' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
electronを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Return `{ action: 'deny' }` from `setWindowOpenHandler` for any content you do not trust, rather than relying on the iframe sandbox alone.パッチが適用されるまでの応急処置として、Return
{ action: 'deny' }fromsetWindowOpenHandlerfor any content you do not trust, rather than relying on the iframe sandbox alone. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade electron to 39.8.10ステージング環境で 39.8.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web github.com