Electron: Permission Check Handler Receives Main Frame Origin Instead of Requesting Iframe Origin
Published 5 Aug 2026 · Updated 5 Aug 2026
Affected packages
- Affected
- <39.8.7
- Fixed in
- 39.8.7
npm install electron@39.8.7- Affected
- >=40.0.0-alpha.1 <40.9.0
- Fixed in
- 40.9.0
npm install electron@40.9.0- Affected
- >=41.0.0-alpha.1 <41.2.0
- Fixed in
- 41.2.0
npm install electron@41.2.0- Affected
- >=42.0.0-alpha.1 <42.0.0-beta.1
- Fixed in
- 42.0.0-beta.1
npm install electron@42.0.0-beta.1Details
Impact
For serial-port and media (camera / microphone) permission checks made from an iframe, the requestingOrigin passed to session.setPermissionCheckHandler was the top-level frame's origin rather than the requesting frame's. Origin-based handler logic could therefore grant a cross-origin iframe device access intended only for the top-level origin.
Apps are only affected if they use setPermissionCheckHandler with origin-based logic and embed cross-origin iframes with delegated device permissions. Apps that base the decision on details.securityOrigin, or that do not embed such iframes, are not affected.
Workarounds
Check details.securityOrigin instead of requestingOrigin for these permissions, or do not delegate device permissions to untrusted iframes.
Fixed Versions
42.0.0-beta.141.2.040.9.039.8.7
For more information
If you have any questions or comments about this advisory, email Electron at [security@electronjs.org](mailto:security@electronjs.org)
Is GHSA-9pf5-hg6p-4pwp in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected electron, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.