Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

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

CVE-2026-34777GHSA-r5p7-gp4j-qhrx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 41.0.0, 40.8.1, 39.8.1, 38.8.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm electron

    Affected
    < 38.8.6>= 39.0.0-alpha.1, < 39.8.1>= 40.0.0-alpha.1, < 40.8.1>= 41.0.0-alpha.1, < 41.0.0
    Fixed in
    41.0.0, 38.8.6, 40.8.1, 39.8.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-34777: 0.12% estimated exploitation activity in the next 30 days; percentile 2.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-r5p7-gp4j-qhrx

  2. Revision 1 · created ·

    Published from osv record GHSA-r5p7-gp4j-qhrx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34777

Advisory: Electron: Incorrect origin passed to permission request handler for iframe requests
IDs: CVE-2026-34777, GHSA-r5p7-gp4j-qhrx
Record: https://patchnext.com/advisories/cve-2026-34777 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 41.0.0, 40.8.1, 39.8.1, 38.8.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected < 38.8.6; >= 39.0.0-alpha.1, < 39.8.1; >= 40.0.0-alpha.1, < 40.8.1; >= 41.0.0-alpha.1, < 41.0.0; fixed in 41.0.0, 38.8.6, 40.8.1, 39.8.1

## Suggested inspection (read-only)
- `npm ls electron --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-r5p7-gp4j-qhrx (OSV record GHSA-r5p7-gp4j-qhrx lists affected ranges: npm electron >=0 =39.0.0-alpha.1 =40.0.0-alpha.1 =41.0.0-alpha.1 <41.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-r5p7-gp4j-qhrx (GitHub-reviewed advisory GHSA-r5p7-gp4j-qhrx lists affected ranges: npm electron >=0 =39.0.0-alpha.1 =40.0.0-alpha.1 =41.0.0-alpha.1 <41.0.0)

Commands are suggestions: review each one before running it.

Loading voting…