dbcve.org
ElectronApplication · Electronjs

CVE-2023-44402

HIGH · 7.0 CVSS v3.1 Published 2023-12-01
Fix available
A fix is available. Upgrade to after 26.2.1 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Electron is an open source framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. 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 `.app` bundle on macOS which these fuses are supposed to protect against. There are no app side workarounds, you must update to a patched version of Electron.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ElectronApplication
Affected:<= 22.3.24>= 23.0.0, <= 23.3.14>= 24.0.0, <= 24.8.3>= 25.0.0, <= 25.8.1>= 26.0.0, <= 26.2.1= 27.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 26.2.1
Vendor patch github.com →
Recommended fix High confidence

Electron 22.3.25+, 23.3.15+, 24.8.4+, or 25.8.2+ (depending on which major version line you are on)

  1. 1. Identify the current Electron version used in your application by checking your package.json or running `electron --version`
  2. 2. For Electron 22.x: upgrade to version 22.3.25 or later
  3. 3. For Electron 23.x: upgrade to version 23.3.15 or later
  4. 4. For Electron 24.x: upgrade to version 24.8.4 or later
  5. 5. For Electron 25.x: upgrade to version 25.8.2 or later
  6. 6. Run `npm install electron@<fixed-version>` or update the electron version in your package.json and run `npm install`
  7. 7. Rebuild and redistribute your application to end users
  8. 8. Ensure the `.app` bundle is deployed to a read-only location on the user's filesystem, as the vulnerability requires the attacker to have write access to the app bundle
Caveat No breaking changes expected; this is a patch release addressing a security vulnerability. However, always test your application with the new Electron version before releasing.

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-44402 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data