CVE-2026-113796

Electron: SameSite cookie restrictions are not applied to windows opened from links

Workarounds

Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content.

Fixed Versions

• 45.0.0-alpha.6
• 44.3.0
• 43.7.0
• 42.11.3

For more information

If you have any questions or comments about this advisory, email us at [email protected]

Pages opened into a new window from a link were loaded as if the app itself had navigated there rather than the page that contained the link, so the request was treated as same-site: SameSite=Strict cookies were sent and Sec-Fetch-Site did not identify the initiating page. Content shown in the app could use this to make a credentialed top-level request to another site that relies on SameSite cookies as a CSRF defence.

Apps are only affected if they load untrusted content and allow it to open new windows. Apps that deny new windows from untrusted content with setWindowOpenHandler are not affected.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2026-113796 has a CVSS score of 4.2 (Medium). The vector is network-reachable, no privileges required, and user interaction required. 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 (45.0.0-alpha.6, 44.3.0, 43.7.0, 42.11.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-113796? CVE-2026-113796 is a medium-severity cross-site request forgery (CSRF) vulnerability in electron (npm), affecting versions >= 45.0.0-alpha.1, < 45.0.0-alpha.6. It is fixed in 45.0.0-alpha.6, 44.3.0, 43.7.0, 42.11.3. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2026-113796? CVE-2026-113796 has a CVSS score of 4.2 (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-113796? electron (npm) versions >= 45.0.0-alpha.1, < 45.0.0-alpha.6 is affected.
4. Is there a fix for CVE-2026-113796? Yes. CVE-2026-113796 is fixed in 45.0.0-alpha.6, 44.3.0, 43.7.0, 42.11.3. Upgrade to this version or later.
5. Is CVE-2026-113796 exploitable, and should I be worried? Whether CVE-2026-113796 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-113796 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-113796?
   • Upgrade electron to 45.0.0-alpha.6 or later
   • Upgrade electron to 44.3.0 or later
   • Upgrade electron to 43.7.0 or later
   • Upgrade electron to 42.11.3 or later

Other vulnerabilities in electron