CVE-2026-70605

Electron: HTTP redirect followed into local file loader

Workarounds

Set redirect: 'error' or redirect: 'manual' on requests to untrusted URLs and validate any redirect target before following it.

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 [email protected]

When following HTTP redirects, net.fetch() and net.request() did not restrict which schemes a redirect could target. A remote server could redirect a request to a local resource, and if the app returns or forwards the response body, local file contents could be disclosed.

Apps are only affected if they make net requests to attacker-influenced URLs with redirects followed (the default) and expose the response body. Apps that only request fixed, trusted URLs are not affected.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-70605 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (39.8.8, 40.9.1, 41.2.1, 42.0.0-beta.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-70605? CVE-2026-70605 is a medium-severity server-side request forgery (SSRF) vulnerability in electron (npm), affecting versions < 39.8.8. It is fixed in 39.8.8, 40.9.1, 41.2.1, 42.0.0-beta.3. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2026-70605? CVE-2026-70605 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of electron are affected by CVE-2026-70605? electron (npm) versions < 39.8.8 is affected.
4. Is there a fix for CVE-2026-70605? Yes. CVE-2026-70605 is fixed in 39.8.8, 40.9.1, 41.2.1, 42.0.0-beta.3. Upgrade to this version or later.
5. Is CVE-2026-70605 exploitable, and should I be worried? Whether CVE-2026-70605 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-70605 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-70605?
   • Upgrade electron to 39.8.8 or later
   • Upgrade electron to 40.9.1 or later
   • Upgrade electron to 41.2.1 or later
   • Upgrade electron to 42.0.0-beta.3 or later

Other vulnerabilities in electron