How severe is GHSA-9pf5-hg6p-4pwp?

GHSA-9pf5-hg6p-4pwp has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-9pf5-hg6p-4pwp?

GHSA-9pf5-hg6p-4pwp affects the following packages: electron (npm), electron (npm), electron (npm), electron (npm). Ecosystems affected: npm.

How do I fix GHSA-9pf5-hg6p-4pwp?

Update electron to 39.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9pf5-hg6p-4pwp is resolved across your whole dependency graph.

How do I detect GHSA-9pf5-hg6p-4pwp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9pf5-hg6p-4pwp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-9pf5-hg6p-4pwp actively exploited in the wild?

No public exploit code has been indexed for GHSA-9pf5-hg6p-4pwp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-9pf5-hg6p-4pwp?

GHSA-9pf5-hg6p-4pwp has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9pf5-hg6p-4pwp?

GHSA-9pf5-hg6p-4pwp is classified as CWE-346 (CWE-346). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9pf5-hg6p-4pwp published, and has it been updated?

GHSA-9pf5-hg6p-4pwp was published on August 5, 2026 and was last updated on August 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

Electron: Permission Check Handler Receives Main Frame Origin Instead of Requesting Iframe OriginGHSA-9pf5-hg6p-4pwp

MEDIUMFix: electron/electron@0cbdf2f

GHSA-9pf5-hg6p-4pwp is a medium-severity (CVSS 5.9) CWE-346 vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Also known asCVE-2026-70599

Published

Aug 5, 2026

Updated

Aug 5, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9pf5-hg6p-4pwp.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-9pf5-hg6p-4pwp by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 388,997 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

electronnpm

8.1Mdownloads / week

Description

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.1
41.2.0
40.9.0
39.8.7

For more information

If you have any questions or comments about this advisory, email Electron at [email protected]

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`electron`	all versions	39.8.7`npm install electron@39.8.7`
📦npm	`electron`	≥ 40.0.0-alpha.1&&< 40.9.0	40.9.0`npm install electron@40.9.0`
📦npm	`electron`	≥ 41.0.0-alpha.1&&< 41.2.0	41.2.0`npm install electron@41.2.0`
📦npm	`electron`	≥ 42.0.0-alpha.1&&< 42.0.0-beta.1	42.0.0-beta.1`npm install electron@42.0.0-beta.1`

Affected Products

1 product · 11 configurations

Application

electronelectronjs

≥ 41.0.0 && < 41.2.1

1 version

42.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update electron to 39.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9pf5-hg6p-4pwp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 if