Vulnerability in electron (CVE-2026-102675)
Summary
Vulnerability in electron (CVE-2026-102675). Confidential information can be exposed externally. Exploitable via protocol.registerFileProtocol. Mitigation: upgrade to 44.0.0-beta.5 or later.
Original description
The description as published by the source.
Impact
Responses served through protocol.registerFileProtocol or protocol.registerHttpProtocol for a custom scheme registered with supportFetchAPI: true but without corsEnabled: true could be read cross-origin by web content. This completes the fix for CVE-2026-70604.
Apps are only affected if they register such a scheme, serve it through one of those handlers, and load untrusted content. Apps that set corsEnabled: true, or that do not load untrusted content, are not affected.
Workarounds
Set corsEnabled: true on the scheme, or do not load untrusted content in windows that can reach it.
Fixed Versions
44.0.0-beta.543.4.142.9.241.10.6
For more information
If you have any questions or comments about this advisory, email us at security@electronjs.org
Source: NIST National Vulnerability Database 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-102675 has been found in electron.
Attackers can target a specific entry point like protocol.registerFileProtocol over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade electron to 44.0.0-beta.5 or later.
If unsure, ask your IT team or search "electron CVE-2026-102675" on the vendor's site.
CVE-2026-102675 (electron) — CWE-346 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: protocol.registerFileProtocol / protocol.registerHttpProtocol
Patched: 44.0.0-beta.5 — apply immediately
Workaround: Set corsEnabled: true on the scheme, or do not load untrusted content in windows that can reach it.
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 protocol.registerFileProtocol without authentication.
Check the vendor advisory for the affected versions of electron. Attack surface: protocol.registerFileProtocol / protocol.registerHttpProtocol.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 44.0.0-beta.5.
Workaround: Set corsEnabled: true on the scheme, or do not load untrusted content in windows that can reach it.
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 the scheme, or do not load untrusted content in windows that can reach it.パッチが適用されるまでの応急処置として、Set
corsEnabled: trueon the scheme, or do not load untrusted content in windows that can reach it. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade electron to 44.0.0-beta.5ステージング環境で 44.0.0-beta.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com