CVE-2026-70610: Electron: contextBridge object copy honors prototype setters

Published Aug 5, 2026
·
Updated

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.4 41.2.2 40.9.2 39.8.9

For more information If you have any questions or comments about this advisory, email Electron at security@electronjs.org

Other sources

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.9, 40.9.2, 41.2.2, and 42.0.0-beta.4, 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, while apps that only accept primitive arguments or validate object arguments are not affected. This issue is fixed in 39.8.9, 40.9.2, 41.2.2, and 42.0.0-beta.4.

— MITRE

Affected Software

16 affected componentsFixes available
npm/electron>=42.0.0-alpha.1<42.0.0-beta.4
42.0.0-beta.4
npm/electron>=41.0.0-alpha.1<41.2.2
41.2.2
npm/electron>=40.0.0-alpha.1<40.9.2
40.9.2
npm/electron<39.8.9
39.8.9
electronjs Electron Node.js<39.8.9
electronjs Electron Node.js>=40.0.0<40.9.2
electronjs Electron Node.js>=41.0.0<41.2.2
electronjs Electron Node.js=42.0.0-alpha1
electronjs Electron Node.js=42.0.0-alpha2
electronjs Electron Node.js=42.0.0-alpha3
electronjs Electron Node.js=42.0.0-alpha4
electronjs Electron Node.js=42.0.0-alpha5
electronjs Electron Node.js=42.0.0-alpha6
electronjs Electron Node.js=42.0.0-beta1
electronjs Electron Node.js=42.0.0-beta2
electronjs Electron Node.js=42.0.0-beta3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 42.0.0-beta.4
  2. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 41.2.2
  3. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 40.9.2
  4. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 39.8.9
  5. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 39.8.9
  6. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 40.9.2
  7. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 41.2.2
  8. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 42.0.0-beta.4
  9. Configuration

    Validate objects received from untrusted content with own-property checks using Object.hasOwn, or copy them onto a null-prototype object before use.

    Electron preload code own-property validation for objects received from untrusted content = Use Object.hasOwn or copy objects onto a null-prototype object

Event History

Aug 5, 2026
CVE Published
via MITRE·05:41 PM
Data Sourced
via MITRE·05:41 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·05:41 PM
Data Sourced
via GitHub·05:41 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·06:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-70610?

CVE-2026-70610 has a medium severity score of 5.4.

2

How does CVE-2026-70610 impact applications using Electron?

CVE-2026-70610 allows attacker-influenced prototypes to potentially compromise preload code in Electron applications.

3

What are the conditions necessary for CVE-2026-70610 to exploit an application?

CVE-2026-70610 affects applications if their preload code accepts object arguments from untrusted content across the contextBridge.

4

How can developers mitigate the risks associated with CVE-2026-70610?

To mitigate CVE-2026-70610, developers should validate and sanitize any object arguments passed into preload code.

5

In which versions of Electron is CVE-2026-70610 present?

CVE-2026-70610 affects specific versions of Electron that allow unsafe behavior in contextBridge interactions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203