How severe is GHSA-jjp3-mq3x-295m?

GHSA-jjp3-mq3x-295m has a CVSS score of 7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jjp3-mq3x-295m?

GHSA-jjp3-mq3x-295m affects the following packages: electron (npm), electron (npm), electron (npm), electron (npm). Ecosystems affected: npm.

How do I fix GHSA-jjp3-mq3x-295m?

Update electron to 38.8.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jjp3-mq3x-295m is resolved across your whole dependency graph.

How do I detect GHSA-jjp3-mq3x-295m 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-jjp3-mq3x-295m if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-jjp3-mq3x-295m actively exploited in the wild?

No public exploit code has been indexed for GHSA-jjp3-mq3x-295m 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-jjp3-mq3x-295m?

GHSA-jjp3-mq3x-295m has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th 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-jjp3-mq3x-295m?

GHSA-jjp3-mq3x-295m is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jjp3-mq3x-295m published, and has it been updated?

GHSA-jjp3-mq3x-295m was published on April 3, 2026 and was last updated on April 6, 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

HIGH severity

Electron: Use-after-free in PowerMonitor on Windows and macOSGHSA-jjp3-mq3x-295m

HIGH

GHSA-jjp3-mq3x-295m is a high-severity (CVSS 7) Use After Free vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Also known asCVE-2026-34770

Published

Apr 3, 2026

Updated

Apr 6, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-jjp3-mq3x-295m.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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

12.5Mdownloads / week

Description

Impact

Apps that use the powerMonitor module may be vulnerable to a use-after-free. After the native PowerMonitor object is garbage-collected, the associated OS-level resources (a message window on Windows, a shutdown handler on macOS) retain dangling references. A subsequent session-change event (Windows) or system shutdown (macOS) dereferences freed memory, which may lead to a crash or memory corruption.

All apps that access powerMonitor events (suspend, resume, lock-screen, etc.) are potentially affected. The issue is not directly renderer-controllable.

Workarounds

There are no app side workarounds, you must update to a patched version of Electron.

Fixed Versions

41.0.0-beta.8
40.8.0
39.8.1
38.8.6

For more information

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

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`electron`	all versions	38.8.6`npm install electron@38.8.6`
📦npm	`electron`	≥ 39.0.0-alpha.1&&< 39.8.1	39.8.1`npm install electron@39.8.1`
📦npm	`electron`	≥ 40.0.0-alpha.1&&< 40.8.0	40.8.0`npm install electron@40.8.0`
📦npm	`electron`	≥ 41.0.0-alpha.1&&< 41.0.0-beta.8	41.0.0-beta.8`npm install electron@41.0.0-beta.8`

Affected Products

1 product · 16 configurations

Application

electronelectronjs

≥ 40.0.0 && < 40.8.0

1 version

41.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 38.8.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jjp3-mq3x-295m is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

### Impact Apps that use the `powerMonitor` module may be vulnerable to a use-after-free. After the native `PowerMonitor` object is garbage-collected, the associated OS-level resources (a message window on Windows, a shutdown handler on macOS) retain dangling references. A subsequent session-change event (Windows) or system shutdown (macOS) dereferences freed memory, which may lead to a crash or memory corruption. All apps that access `powerMonitor` events (`suspend`, `resume`, `lock-screen`, etc.) are potentially affected. The issue is not directly renderer-controllable. ### Workarounds The