Electron: Incorrect origin passed to permission request handler for iframe requests

中 5.4CVE-2026-34777 · GHSA-r5p7-gp4j-qhrx · 04/04/2026 公開 · 24/07/2026 更新

要点

CVE-2026-34777 は electron (electronjs), electron に影響する深刻度「中」 (CVSS 5.4) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.12%（全脆弱性の 2.1% より高い）。
対処：39.8.1, 40.8.1, 38.8.6, 41.0.0 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
electron electronjs	`= 41.0.0≥ 39.0.0, < 39.8.1≥ 40.0.0, < 40.8.1< 38.8.6`	`39.8.140.8.138.8.6`
electron npm	`≥ 39.0.0-alpha.1, < 39.8.1≥ 40.0.0-alpha.1, < 40.8.1≥ 41.0.0-alpha.1, < 41.0.0< 38.8.6`	`39.8.140.8.141.0.038.8.6`

概要

Impact

When an iframe requests fullscreen, pointerLock, keyboardLock, openExternal, or media permissions, the origin passed to session.setPermissionRequestHandler() was the top-level page's origin rather than the requesting iframe's origin. Apps that grant permissions based on the origin parameter or webContents.getURL() may inadvertently grant permissions to embedded third-party content.

The correct requesting URL remains available via details.requestingUrl. Apps that already check details.requestingUrl are not affected.

Workarounds

In your setPermissionRequestHandler, inspect details.requestingUrl rather than the origin parameter or webContents.getURL() when deciding whether to grant fullscreen, pointerLock, keyboardLock, openExternal, or media permissions.

Fixed Versions

41.0.0
40.8.1
39.8.1
38.8.6

For more information

If there are any questions or comments about this advisory, please email [email protected]

NVD の説明

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.1, 40.8.1, and 41.0.0, when an iframe requests fullscreen, pointerLock, keyboardLock, openExternal, or media permissions, the origin passed to session.setPermissionRequestHandler() was the top-level page's origin rather than the requesting iframe's origin. Apps that grant permissions based on the origin parameter or webContents.getURL() may inadvertently grant permissions to embedded third-party content. The correct requesting URL remains available via details.requestingUrl. Apps that already check details.requestingUrl are not affected. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.1, and 41.0.0.