CVE-2026-70602: Electron: Extension tab APIs operate across session boundaries

Published Aug 5, 2026
·
Updated

Impact Extension tab and scripting APIs were not scoped to the extension's own session. A malicious or compromised extension loaded into one session could navigate, script, and read from windows belonging to a different session.

Apps are only affected if they load Chrome extensions via session.loadExtension and rely on separate sessions to isolate that extension from other content. Apps that do not load extensions, or that use a single session, are not affected.

Workarounds Only load extensions from sources you trust; do not rely on session separation alone to contain an extension.

Fixed Versions 42.0.0-beta.3 41.2.1 40.9.0 39.8.8

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.8, 40.9.0, 41.2.1, and 42.0.0-beta.3, extension tab and scripting APIs were not scoped to the extension's own session. A malicious or compromised extension loaded into one session could navigate, script, and read from windows belonging to a different session. Apps are only affected if they load Chrome extensions via session.loadExtension and rely on separate sessions to isolate that extension from other content. This issue is fixed in versions 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.

— MITRE

Affected Software

15 affected componentsFixes available
npm/electron>=42.0.0-alpha.1<42.0.0-beta.3
42.0.0-beta.3
npm/electron>=41.0.0-alpha.1<41.2.1
41.2.1
npm/electron>=40.0.0-alpha.1<40.9.0
40.9.0
npm/electron<39.8.8
39.8.8
electronjs Electron Node.js<39.8.8
electronjs Electron Node.js>=40.0.0<40.9.0
electronjs Electron Node.js>=41.0.0<41.2.1
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

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.3
  2. Upgrade

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

    Fixed in 41.2.1
  3. Upgrade

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

    Fixed in 40.9.0
  4. Upgrade

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

    Fixed in 39.8.8
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 39.8.8
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 40.9.0
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 41.2.1
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 42.0.0-beta.3
  9. Compensating control

    Only load extensions from sources you trust; do not rely on session separation alone to contain an extension.

Event History

Aug 5, 2026
CVE Published
via MITRE·03:54 PM
Data Sourced
via MITRE·03:54 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·03:57 PM
Data Sourced
via GitHub·03:57 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-70602?

The severity of CVE-2026-70602 is rated as medium with a score of 6.6.

2

What is the impact of CVE-2026-70602?

CVE-2026-70602 allows a malicious or compromised extension to navigate, script, and read from windows belonging to a different session.

3

Which software is affected by CVE-2026-70602?

CVE-2026-70602 affects applications that load Chrome extensions via npm or Electron.

4

How do I fix CVE-2026-70602?

To fix CVE-2026-70602, ensure that you are updating to the latest version of the Electron framework that includes security patches.

5

What are the risks associated with CVE-2026-70602?

The risks associated with CVE-2026-70602 include unauthorized access and manipulation of content in different browser sessions.

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