Skip to content
Fencer Intel
medium 4.2

CVE-2026-113796 json

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

published 19d ago modified 17d ago also EUVD-2026-107368 , GHSA-2p8c-gr87-2676

cvss
4.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.6, Electron treated pages opened into a new window from links as application-initiated navigations instead of preserving the page containing the link as the initiator. The resulting top-level request could be classified as same-site, causing SameSite=Strict cookies to be sent and Sec-Fetch-Site not to identify the initiating page. An application that loads untrusted content and permits it to open new windows could therefore allow that content to make a credentialed request to another site that relies on SameSite cookies for CSRF protection. This issue is fixed in versions 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.6.

Patch / fix

  • npm electron 42.11.3, 43.7.0, 44.3.0, 45.0.0-alpha.6
  • electronjs electron 42.11.3, 43.7.0, 44.3.0, 45.0.0-alpha.6
  • atom electron 42.11.3, 43.7.0, 44.3.0, 45.0.0-alpha.6
  • mozilla firefox 42.11.3, 43.7.0, 44.3.0, 45.0.0-alpha.6

Is CVE-2026-113796 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-113796 updated cvss 4.2

electron: electron: SameSite cookie bypass via incorrect navigation initiator handling

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
17d ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.2 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
GitHub 3.1 4.2 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm electron
>=45.0.0-alpha.1, <45.0.0-alpha.6
>=44.0.0-alpha.1, <44.3.0
>=43.0.0-alpha.1, <43.7.0
<42.11.3
45.0.0-alpha.6
44.3.0
43.7.0
42.11.3

Affected products

  • electron electron

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.