Electron up to 42.11.8/43.7.5/44.4.x/45.0.0-alpha.12 PointerLock session.setPermissionRequestHandler isMainFrame cross-domain policy

Summaryinfo

A vulnerability was found in Electron up to 42.11.8/43.7.5/44.4.x/45.0.0-alpha.12. It has been classified as problematic. Impacted is the function session.setPermissionRequestHandler of the component PointerLock. This manipulation of the argument isMainFrame causes cross-domain policy. This vulnerability is handled as CVE-2026-113798. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic was found in Electron up to 42.11.8/43.7.5/44.4.x/45.0.0-alpha.12. Affected by this vulnerability is the function session.setPermissionRequestHandler of the component PointerLock. The manipulation of the argument isMainFrame with an unknown input leads to a cross-domain policy vulnerability. The CWE definition for the vulnerability is CWE-942. The product uses a cross-domain policy file that includes domains that should not be trusted. As an impact it is known to affect confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-113798 since 10/20/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 42.11.9, 43.7.6, 44.5.0 or 45.0.0-alpha.13 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Electron

Version

• 42.11.0
• 42.11.1
• 42.11.2
• 42.11.3
• 42.11.4
• 42.11.5
• 42.11.6
• 42.11.7
• 42.11.8
• 43.7.0
• 43.7.1
• 43.7.2
• 43.7.3
• 43.7.4
• 43.7.5
• 44.0
• 44.1
• 44.2
• 44.3
• 44.4
• 45.0.0-alpha.0
• 45.0.0-alpha.1
• 45.0.0-alpha.2
• 45.0.0-alpha.3
• 45.0.0-alpha.4
• 45.0.0-alpha.5
• 45.0.0-alpha.6
• 45.0.0-alpha.7
• 45.0.0-alpha.8
• 45.0.0-alpha.9
• 45.0.0-alpha.10
• 45.0.0-alpha.11
• 45.0.0-alpha.12

Website

• Product: https://github.com/electron/electron/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion