How severe is GHSA-7m48-wc93-9g85?

GHSA-7m48-wc93-9g85 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-7m48-wc93-9g85?

GHSA-7m48-wc93-9g85 affects the following packages: electron (npm), electron (npm), electron (npm), electron (npm), electron (npm), electron (npm). Ecosystems affected: npm.

How do I fix GHSA-7m48-wc93-9g85?

Update electron to 22.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7m48-wc93-9g85 is resolved across your whole dependency graph.

How do I detect GHSA-7m48-wc93-9g85 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-7m48-wc93-9g85 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-7m48-wc93-9g85 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7m48-wc93-9g85 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-7m48-wc93-9g85?

GHSA-7m48-wc93-9g85 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 11th 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-7m48-wc93-9g85?

GHSA-7m48-wc93-9g85 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7m48-wc93-9g85 published, and has it been updated?

GHSA-7m48-wc93-9g85 was published on December 1, 2023 and was last updated on September 10, 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

ASAR Integrity bypass via filetype confusion in electronGHSA-7m48-wc93-9g85

MEDIUMFix: electron/electron#39788

GHSA-7m48-wc93-9g85 is a medium-severity (CVSS 6.1) CWE-345 vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Also known asCVE-2023-44402

Published

Dec 1, 2023

Updated

Sep 10, 2026

Affected

6 pkgs

Patched

5 / 6

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs11th percentile — riskier than 11% 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

6 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

This only impacts apps that have the embeddedAsarIntegrityValidation and onlyLoadAppFromAsar fuses enabled. Apps without these fuses enabled are not impacted. This issue is specific to macOS as these fuses are only currently supported on macOS.

Specifically this issue can only be exploited if your app is launched from a filesystem the attacker has write access too. i.e. the ability to edit files inside the resources folder in your app installation on Windows which these fuses are supposed to protect against.

Workarounds

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

Fixed Versions

27.0.0-alpha.7
26.2.1
25.8.1
24.8.3
22.3.24

For more information

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

Affected Packages

6 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`electron`	all versions	22.3.24`npm install electron@22.3.24`
📦npm	`electron`	≥ 24.0.0-alpha.1&&< 24.8.3	24.8.3`npm install electron@24.8.3`
📦npm	`electron`	≥ 25.0.0-alpha.1&&< 25.8.1	25.8.1`npm install electron@25.8.1`
📦npm	`electron`	≥ 26.0.0-alpha.1&&< 26.2.1	26.2.1`npm install electron@26.2.1`
📦npm	`electron`	≥ 27.0.0-alpha.1&&< 27.0.0-alpha.7	27.0.0-alpha.7`npm install electron@27.0.0-alpha.7`
📦npm	`electron`	≥ 23.0.0-alpha.1	No fix

Affected Products

1 product · 11 configurations

Application

electronelectronjs

≥ 26.0.0 && ≤ 26.2.1

1 version

27.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 22.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7m48-wc93-9g85 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 This only impacts apps that have the `embeddedAsarIntegrityValidation` and `onlyLoadAppFromAsar` [fuses](https://www.electronjs.org/docs/latest/tutorial/fuses) enabled. Apps without these fuses enabled are not impacted. This issue is specific to macOS as these fuses are only currently supported on macOS. Specifically this issue can only be exploited if your app is launched from a filesystem the attacker has write access too. i.e. the ability to edit files inside the `resources` folder in your app installation on Windows which these fuses are supposed to protect against. ### Wor