Vulnerability in electron (CVE-2026-102677)
Summary
Vulnerability in electron (CVE-2026-102677). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 44.0.0-beta.6 or later.
Original description
The description as published by the source.
Impact
The cache Electron keeps for sandboxed preload scripts did not verify that a cached entry matched the preload it was served for. A compromised renderer could use this to run its own code in the preload context on a later load.
Apps are only affected if they load untrusted content. Apps that do not load untrusted content are not affected.
Workarounds
There are no app side workarounds, you must update to a patched version of Electron.
Fixed Versions
44.0.0-beta.643.5.042.10.0
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-102677 has been found in electron.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade electron to 44.0.0-beta.6 or later.
If unsure, ask your IT team or search "electron CVE-2026-102677" on the vendor's site.
CVE-2026-102677 (electron) — CWE-20 / CVSS v3 7.8
Attack vector: local / no user interaction
Patched: 44.0.0-beta.6 — apply immediately
Workaround: There are no app side workarounds, you must update to a patched version of Electron.
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-20) exists in electron.
Check the vendor advisory for the affected versions of electron.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 44.0.0-beta.6.
Workaround: There are no app side workarounds, you must update to a patched version of Electron.
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
There are no app side workarounds, you must update to a patched version of Electron.パッチが適用されるまでの応急処置として、There are no app side workarounds, you must update to a patched version of Electron. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade electron to 44.0.0-beta.6ステージング環境で 44.0.0-beta.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 github.com
- web github.com