Vulnerability in electron (CVE-2026-70610)
Summary
Vulnerability in electron (CVE-2026-70610). Risk of unauthorized operations or information disclosure. Exploitable via contextBridge. Mitigation: upgrade to 42.0.0-beta.4 or later.
Original description
The description as published by the source.
Impact
Objects copied across the contextBridge boundary from untrusted content could carry an attacker-influenced prototype, enabling prototype-pollution-style attacks against preload code despite context isolation being enabled.
Apps are only affected if their preload code accepts object arguments from untrusted content and reads properties from them without own-property checks. Apps that only accept primitive arguments, or that validate object arguments, are not affected.
Workarounds
Validate objects received from untrusted content with own-property checks (Object.hasOwn), or copy them onto a null-prototype object before use.
Fixed Versions
42.0.0-beta.441.2.240.9.239.8.9
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-70610 has been found in electron.
Attackers can target a specific entry point like contextBridge over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade electron to 42.0.0-beta.4 or later.
If unsure, ask your IT team or search "electron CVE-2026-70610" on the vendor's site.
CVE-2026-70610 (electron) — CWE-1321 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: contextBridge / Object.hasOwn
Patched: 42.0.0-beta.4 — apply immediately
Workaround: Validate objects received from untrusted content with own-property checks (Object.hasOwn), or copy them onto a null-prototype object before use.
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-1321) exists in electron. Attackers reach the vulnerable code path via contextBridge without authentication.
Check the vendor advisory for the affected versions of electron. Attack surface: contextBridge / Object.hasOwn.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 42.0.0-beta.4.
Workaround: Validate objects received from untrusted content with own-property checks (Object.hasOwn), or copy them onto a null-prototype object before use.
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
Validate objects received from untrusted content with own-property checks (`Object.hasOwn`), or copy them onto a null-prototype object before use.パッチが適用されるまでの応急処置として、Validate objects received from untrusted content with own-property checks (
Object.hasOwn), or copy them onto a null-prototype object before use. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade electron to 42.0.0-beta.4ステージング環境で 42.0.0-beta.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- 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
- 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