CVE-2026-34777: Electron: Incorrect origin passed to permission request handler for iframe requests

Published Apr 3, 2026
·
Updated

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 security@electronjs.org

Other sources

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.

MITRE

Affected Software

21 affected componentsFixes available
npm/electron>=41.0.0-alpha.1<41.0.0
41.0.0
npm/electron>=40.0.0-alpha.1<40.8.1
40.8.1
npm/electron>=39.0.0-alpha.1<39.8.1
39.8.1
npm/electron<38.8.6
38.8.6
electronjs Electron Node.js<38.8.6
electronjs Electron Node.js>=39.0.0<39.8.1
electronjs Electron Node.js>=40.0.0<40.8.1
electronjs Electron Node.js=41.0.0-alpha1
electronjs Electron Node.js=41.0.0-alpha2
electronjs Electron Node.js=41.0.0-alpha3
electronjs Electron Node.js=41.0.0-alpha4
electronjs Electron Node.js=41.0.0-alpha5
electronjs Electron Node.js=41.0.0-alpha6
electronjs Electron Node.js=41.0.0-beta1
electronjs Electron Node.js=41.0.0-beta2
electronjs Electron Node.js=41.0.0-beta3
electronjs Electron Node.js=41.0.0-beta4
electronjs Electron Node.js=41.0.0-beta5
electronjs Electron Node.js=41.0.0-beta6
electronjs Electron Node.js=41.0.0-beta7
electronjs Electron Node.js=41.0.0-beta8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 41.0.0
  2. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 40.8.1
  3. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 39.8.1
  4. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 38.8.6
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 38.8.6
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 39.8.1
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 40.8.1
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 41.0.0
  9. Configuration

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

    Electron setPermissionRequestHandler Use details.requestingUrl for permission decisions = Inspect details.requestingUrl rather than origin parameter or webContents.getURL()

Event History

Apr 3, 2026
Advisory Published
via GitHub·02:44 AM
Data Sourced
via GitHub·02:44 AM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·11:57 PM
Data Sourced
via MITRE·11:57 PM
DescriptionSeverityWeakness
Apr 4, 2026
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203