{"id":"ghsa-ghsa-x562-297c-g43g","seq":309557,"kind":"advisory","title":"Electron: Pointer lock permission requests can be attributed to the wrong frame","url":"https://github.com/advisories/GHSA-x562-297c-g43g","permalink":"https://vulnpulse.app/items/ghsa-ghsa-x562-297c-g43g","summary":"影響: 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\nFor 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…","severity":"medium","techs":["nodejs","electron"],"cves":["CVE-2026-113798"],"tags":["GHSA-x562-297c-g43g","electron","electron","electron","electron"],"source":{"id":"ghsa","name":"GitHub Advisory Database"},"published_at":"2026-10-22T16:47:15.000Z","fetched_at":"2026-10-22T20:09:55.169Z"}