CVE-2026-70604: High severity npm/electron vulnerability

Published Aug 5, 2026
·
Updated

Impact A custom scheme registered with supportFetchAPI: true but without corsEnabled: true was not subject to CORS enforcement. A page loaded from a remote origin could therefore fetch() or XMLHttpRequest that scheme cross-origin and read the full response body, rather than the read being blocked.

Apps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set corsEnabled: true, or that do not load untrusted content, are not affected.

Workarounds Set corsEnabled: true on schemes that must enforce CORS, and validate the request Origin in your protocol handler before returning sensitive data.

Fixed Versions 42.0.0 41.4.0 40.9.3 39.8.10

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

Affected Software

4 affected componentsFixes available
npm/electron<39.8.10
39.8.10
npm/electron>=40.0.0-alpha.1<40.9.3
40.9.3
npm/electron>=41.0.0-alpha.1<41.4.0
41.4.0
npm/electron>=42.0.0-alpha.1<42.0.0
42.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 39.8.10
  2. Upgrade

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

    Fixed in 40.9.3
  3. Upgrade

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

    Fixed in 41.4.0
  4. Upgrade

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

    Fixed in 42.0.0
  5. Upgrade

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

    Fixed in 39.8.10
  6. Upgrade

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

    Fixed in 40.9.3
  7. Upgrade

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

    Fixed in 41.4.0
  8. Upgrade

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

    Fixed in 42.0.0
  9. Configuration

    For any custom scheme that must enforce CORS, set `corsEnabled: true` (in the scheme registration) so the scheme is subject to CORS enforcement.

    Electron custom scheme (protocol handler) corsEnabled = true
  10. Configuration

    In your protocol handler, validate the request `Origin` before returning sensitive data.

    Electron custom scheme (protocol handler) Origin validation = required

Event History

Aug 5, 2026
Advisory Published
via GitHub·03:59 PM
Data Sourced
via GitHub·03:59 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Company

Resources

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