Vulnerability in electron (CVE-2026-70604)
Summary
Vulnerability in electron (CVE-2026-70604). Confidential information can be exposed externally. Exploitable via XMLHttpRequest. Mitigation: upgrade to 39.8.10 or later.
Original description
The description as published by the source.
Impact
A custom scheme registered with supportFetchAPI: true but without corsEnabled: true was not subject to CORS enforcement. A page loaded from a remote origin could therefore fetch() or XMLHttpRequest that scheme cross-origin and read the full response body, rather than the read being blocked.
Apps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set corsEnabled: true, or that do not load untrusted content, are not affected.
Workarounds
Set corsEnabled: true on schemes that must enforce CORS, and validate the request Origin in your protocol handler before returning sensitive data.
Fixed Versions
42.0.041.4.040.9.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-70604 has been found in electron.
Attackers can target a specific entry point like XMLHttpRequest over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade electron to 39.8.10 or later.
If unsure, ask your IT team or search "electron CVE-2026-70604" on the vendor's site.
CVE-2026-70604 (electron) — CWE-942 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: XMLHttpRequest / Origin
Patched: 39.8.10 — apply immediately
Workaround: Set corsEnabled: true on schemes that must enforce CORS, and validate the request Origin in your protocol handler before returning sensitive data.
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-942) exists in electron. Attackers reach the vulnerable code path via XMLHttpRequest without authentication.
Check the vendor advisory for the affected versions of electron. Attack surface: XMLHttpRequest / Origin.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 39.8.10.
Workaround: Set corsEnabled: true on schemes that must enforce CORS, and validate the request Origin in your protocol handler before returning sensitive data.
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 `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data.パッチが適用されるまでの応急処置として、Set
corsEnabled: trueon schemes that must enforce CORS, and validate the requestOriginin your protocol handler before returning sensitive data. を実施。回避策の副作用 (機能低下) を確認した上で。 -
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
- package github.com
- patch security-advisories@github.com
- web github.com