GHSA-x562-297c-g43g CVE-2026-113798

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

Medium npm

Severity: 5.4 / 10; Medium · CVSS 3.1
Exploit chance (EPSS): 0.24%; Chance of exploitation in the next 30 days. Higher than 15.61% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-346 Origin Validation Error
Fix: 45.0.0-alpha.13; Upgrade electron to this version or later

Description

Impact

For pointerLock permission requests made from some cross-origin iframes, session.setPermissionRequestHandler() was given the top-level frame's requestingUrl and isMainFrame instead of the requesting frame's. Apps that grant pointer lock based on the requesting origin could grant it to embedded content under the top-level page's identity.

Apps are only affected if they embed untrusted content in iframes and decide pointerLock requests by origin in setPermissionRequestHandler. Apps that do not embed untrusted content, or that deny pointerLock for it, are not affected.

Workarounds

Deny the pointerLock permission for web contents that embed untrusted frames.

Fixed Versions

45.0.0-alpha.13
44.5.0
43.7.6
42.11.9

For more information

If you have any questions or comments about this advisory, email us at security@electronjs.org

Affected versions

npm

Package	Vulnerable	Fixed in
electron	`>= 45.0.0-alpha.1, < 45.0.0-alpha.13`	`45.0.0-alpha.13`
electron	`>= 44.0.0-alpha.1, < 44.5.0`	`44.5.0`
electron	`>= 43.0.0-alpha.1, < 43.7.6`	`43.7.6`
electron	`< 42.11.9`	`42.11.9`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

electron npm → `45.0.0-alpha.13`

npm

npm install electron@45.0.0-alpha.13

yarn

yarn add electron@45.0.0-alpha.13

pnpm

pnpm add electron@45.0.0-alpha.13

Severity breakdown

CVSS 3.1 5.4

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Weakness

CWE-346: Origin Validation Error

The product does not properly verify that the source of data or communication is valid.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2026-113798

Packages

github.com/electron/electron

Timeline

Oct 21, 2026 Published
Oct 28, 2026 Last updated by the source
Nov 1, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-qqvq-6xgj-jw8g Electron affected by libvpx's heap buffer overflow in vp8 encoding	High Known exploited	Also affects electron
GHSA-j7hp-h8jx-5ppr libwebp: OOB write in BuildHuffmanTable	High Known exploited	Also affects electron
GHSA-995f-9x5r-2rcj Heap buffer overflow in GPU	Critical Known exploited	Also affects electron
GHSA-jr5w-w6x2-84p9 Electron: Mitigation for compromised eMudhra intermediate certificates	High	Also affects electron
GHSA-h3v5-h239-pg29 Electron: Off-screen rendering on macOS trusts GPU-supplied frame geometry	Low	Also affects electron
GHSA-3qxv-5xgr-q7w9 Electron: Frame subscription trusts GPU-supplied frame geometry	Low	Also affects electron
GHSA-997q-gvvc-jwmx Electron: openExternal permission requests can be attributed to the wrong origin	Medium	Also affects electron
GHSA-fw47-9c62-h3vw Electron: HID and USB permission checks can be attributed to the wrong origin	Medium	Also affects electron

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor