Is CVE-2026-70610 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-70610 being exploited in the wild.

How severe is CVE-2026-70610?

Medium severity, with a CVSS score of 5.4, published 5 August 2026.

Which products and versions are affected?

electron (npm) SEMVER:introduced=0,fixed=39.8.9.

Is there a fix for CVE-2026-70610?

Yes. electron (npm): upgrade to 39.8.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-70610 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-70610?

Check whether you run electron (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-70610: Electron prototype pollution in contextBridge object copying

CVE-2026-70610 · Severity: medium · CVSS 5.4 · Published 2026-08-05

Electron, a framework used to build desktop applications with web technologies, contains a vulnerability in how it handles data passed between untrusted web content and the application's internal code. An attacker could potentially manipulate the way objects are processed to bypass security boundaries, leading to unauthorized actions within the application. This issue primarily affects applications that process complex data objects from untrusted sources without strict validation.

Technologies: electron (npm). Vendors: npm.

Quick answers

Is CVE-2026-70610 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-70610 being exploited in the wild.
How severe is CVE-2026-70610?: Medium severity, with a CVSS score of 5.4, published 5 August 2026.
Which products and versions are affected?: electron (npm) SEMVER:introduced=0,fixed=39.8.9.
Is there a fix for CVE-2026-70610?: Yes. electron (npm): upgrade to 39.8.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-70610 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-70610?: Check whether you run electron (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

electron (npm): upgrade to 39.8.9 or later
```
npm install electron@39.8.9
```

Technical details

A prototype pollution vulnerability exists in Electron's contextBridge. When objects are copied across the contextBridge boundary from untrusted content, the copying process incorrectly honors prototype setters. This allows an attacker to influence the prototype of objects in the privileged preload script, even when context isolation is enabled. The vulnerability is exploitable if the preload code accepts object arguments from untrusted content and accesses their properties without performing own-property checks (e.g., Object.hasOwn). The fix involves using CreateDataProperty during the object copying process to ensure properties are defined directly on the target object rather than triggering setters.

Affected products

Electron electron < 39.8.9, >= 40.0.0-alpha.1, < 40.9.2, >= 41.0.0-alpha.1, < 41.2.2, >= 42.0.0-alpha.1, < 42.0.0-beta.4

Identifiers

CVE-2026-70610
GHSA-ff2p-hmqr-hxm4

Timeline

2026-04-16: patched: Fixes merged into various release branches
2026-07-27: disclosed
2026-08-05: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.