cve.bz

CVE-2026-70605 electronjs electron: SSRF

5.9 mediumEPSS 0.3%Fix available

Medium (5.9) in electronjs electron. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in electron 39.8.8, 40.9.1, 41.2.1.

On this page
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, 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 and expose the response body. This issue is fixed in versions 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-70605 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-70605?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-70605?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-70605 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
electronjs:electronbefore 39.8.8
electronjs:electronfrom 40.0.0 before 40.9.0
electronjs:electronfrom 41.0.0 before 41.2.1
electronjs:electron42.0.0:alpha1
electronjs:electron42.0.0:alpha2
electronjs:electron42.0.0:alpha3
electronjs:electron42.0.0:alpha4
electronjs:electron42.0.0:alpha5
electronjs:electron42.0.0:alpha6
electronjs:electron42.0.0:beta1
electronjs:electron42.0.0:beta2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v64r-4m7r-3mvqnpmelectron<39.8.839.8.8
GHSA-v64r-4m7r-3mvqnpmelectron>=40.0.0-alpha.1 <40.9.140.9.1
GHSA-v64r-4m7r-3mvqnpmelectron>=41.0.0-alpha.1 <41.2.141.2.1
GHSA-v64r-4m7r-3mvqnpmelectron>=42.0.0-alpha.1 <42.0.0-beta.342.0.0-beta.3

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON