Skip to content
Fencer Intel
medium 5.4

CVE-2026-113798 json

Electron: Pointer lock permission requests can be attributed to the wrong frame

published 19d ago modified 13d ago also EUVD-2026-107374 , GHSA-x562-297c-g43g

cvss
5.4
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 15%
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.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13, pointerLock permission requests from some cross-origin iframes caused session.setPermissionRequestHandler() to receive the top-level frame's requestingUrl and isMainFrame values instead of those of the requesting frame. An application that embeds untrusted iframe content and grants pointer lock based on the requesting origin could therefore grant the permission under the top-level page's identity. Applications that deny pointerLock for untrusted embedded content are not affected. This issue is fixed in versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13.

Patch / fix

  • npm electron 42.11.9, 43.7.6, 44.5.0, 45.0.0-alpha.13
  • electronjs electron 42.11.9, 43.7.6, 44.5.0, 45.0.0-alpha.13
  • atom electron 42.11.9, 43.7.6, 44.5.0, 45.0.0-alpha.13
  • mozilla firefox 42.11.9, 43.7.6, 44.5.0, 45.0.0-alpha.13

Is CVE-2026-113798 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-113798 updated cvss 5.4

electron: Electron: Unauthorized pointer lock permission grant via cross-origin iframes

  • 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
13d ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
npm electron
>=45.0.0-alpha.1, <45.0.0-alpha.13
>=44.0.0-alpha.1, <44.5.0
>=43.0.0-alpha.1, <43.7.6
<42.11.9
45.0.0-alpha.13
44.5.0
43.7.6
42.11.9

Affected products

  • electron electron

Classification

Weakness

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.