Vulnerability in electron (CVE-2026-70606)
Summary
Vulnerability in electron (CVE-2026-70606). Confidential information can be exposed externally. Exploitable via ProtocolResponse. Mitigation: upgrade to 40.10.6 or later.
Original description
The description as published by the source.
Impact
When a custom protocol handler returned a ProtocolResponse with a url and no session, Electron made the upstream request through defaultSession instead of the session that handled the protocol. A cached response could then be reused across otherwise isolated session partitions.
Apps that use ProtocolResponse.url, omit ProtocolResponse.session, and rely on separate sessions to isolate content are affected. Apps that set an explicit session, or that do not isolate content across sessions, are not affected.
Workarounds
Set ProtocolResponse.session explicitly so the request uses the intended session's cache.
Fixed Versions
43.0.042.5.141.9.140.10.6
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-70606 has been found in electron.
Attackers can target a specific entry point like ProtocolResponse over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade electron to 40.10.6 or later.
If unsure, ask your IT team or search "electron CVE-2026-70606" on the vendor's site.
CVE-2026-70606 (electron) — CWE-668 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: ProtocolResponse / url / session / defaultSession
Patched: 40.10.6 — apply immediately
Workaround: Set ProtocolResponse.session explicitly so the request uses the intended session's cache.
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-668) exists in electron. Attackers reach the vulnerable code path via ProtocolResponse without authentication.
Check the vendor advisory for the affected versions of electron. Attack surface: ProtocolResponse / url / session / defaultSession.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 40.10.6.
Workaround: Set ProtocolResponse.session explicitly so the request uses the intended session's cache.
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
Set `ProtocolResponse.session` explicitly so the request uses the intended session's cache.パッチが適用されるまでの応急処置として、Set
ProtocolResponse.sessionexplicitly so the request uses the intended session's cache. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade electron to 40.10.6ステージング環境で 40.10.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- patch security-advisories@github.com
- web github.com