Vulnerability in electron (CVE-2026-102674)
Summary
Vulnerability in electron (CVE-2026-102674). Confidential information can be exposed externally. Exploitable via sandbox. Mitigation: upgrade to 44.0.0-beta.5 or later.
Original description
The description as published by the source.
Impact
Windows opened from a sandboxed top-level document did not inherit that document's HTML sandbox restrictions, so content that was meant to run sandboxed could open a window with the app's full origin. GHSA-hq2x-r82h-9wj4 covers the same issue for sandboxed iframes.
Apps are only affected if they render untrusted content in a sandboxed top-level document that allows popups. Apps that deny popups from untrusted content with setWindowOpenHandler are not affected.
Workarounds
Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content.
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-102674 has been found in electron.
Attackers can target a specific entry point like sandbox over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/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-102674" on the vendor's site.
CVE-2026-102674 (electron) — CWE-266 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: sandbox / setWindowOpenHandler
Patched: 44.0.0-beta.5 — apply immediately
Workaround: Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content.
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-266) exists in electron. Attackers reach the vulnerable code path via sandbox without authentication.
Check the vendor advisory for the affected versions of electron. Attack surface: sandbox / setWindowOpenHandler.
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to 44.0.0-beta.5.
Workaround: Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content.
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 windows opened by untrusted content.パッチが適用されるまでの応急処置として、Return
{ action: 'deny' }fromsetWindowOpenHandlerfor windows opened by untrusted content. を実施。回避策の副作用 (機能低下) を確認した上で。 -
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
- 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 security-advisories@github.com
- web github.com