Vulnerability in electron (CVE-2026-70599)
Summary
Vulnerability in electron (CVE-2026-70599). Confidential information can be exposed externally. Exploitable via requestingOrigin. Mitigation: upgrade to 42.0.0-beta.1 or later.
Original description
The description as published by the source.
Impact
For serial-port and media (camera / microphone) permission checks made from an iframe, the requestingOrigin passed to session.setPermissionCheckHandler was the top-level frame's origin rather than the requesting frame's. Origin-based handler logic could therefore grant a cross-origin iframe device access intended only for the top-level origin.
Apps are only affected if they use setPermissionCheckHandler with origin-based logic and embed cross-origin iframes with delegated device permissions. Apps that base the decision on details.securityOrigin, or that do not embed such iframes, are not affected.
Workarounds
Check details.securityOrigin instead of requestingOrigin for these permissions, or do not delegate device permissions to untrusted iframes.
Fixed Versions
42.0.0-beta.141.2.040.9.039.8.7
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-70599 has been found in electron.
Attackers can target a specific entry point like requestingOrigin over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade electron to 42.0.0-beta.1 or later.
If unsure, ask your IT team or search "electron CVE-2026-70599" on the vendor's site.
CVE-2026-70599 (electron) — CWE-346 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: requestingOrigin / session.setPermissionCheckHandler / setPermissionCheckHandler / details.securityOrigin
Patched: 42.0.0-beta.1 — apply immediately
Workaround: Check details.securityOrigin instead of requestingOrigin for these permissions, or do not delegate device permissions to untrusted iframes.
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-346) exists in electron. Attackers reach the vulnerable code path via requestingOrigin without authentication.
Check the vendor advisory for the affected versions of electron. Attack surface: requestingOrigin / session.setPermissionCheckHandler / setPermissionCheckHandler / details.securityOrigin.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 42.0.0-beta.1.
Workaround: Check details.securityOrigin instead of requestingOrigin for these permissions, or do not delegate device permissions to untrusted iframes.
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
Check `details.securityOrigin` instead of `requestingOrigin` for these permissions, or do not delegate device permissions to untrusted iframes.パッチが適用されるまでの応急処置として、Check
details.securityOrigininstead ofrequestingOriginfor these permissions, or do not delegate device permissions to untrusted iframes. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade electron to 42.0.0-beta.1ステージング環境で 42.0.0-beta.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web github.com