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

- 種別: advisory
- 重大度: medium
- 関連技術: nodejs, electron
- CVE: CVE-2026-113798
- 公開日時: 2026-10-22T16:47:15.000Z
- 情報源: GitHub Advisory Database (https://github.com/advisories/GHSA-x562-297c-g43g)
- パーマリンク: https://vulnpulse.app/items/ghsa-ghsa-x562-297c-g43g

影響: npm:electron >= 45.0.0-alpha.1, < 45.0.0-alpha.13 → 45.0.0-alpha.13, npm:electron >= 44.0.0-alpha.1, < 44.5.0 → 44.5.0, npm:electron >= 43.0.0-alpha.1, < 43.7.6 → 43.7.6, npm:electron < 42.11.9 → 42.11.9
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 em…