Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and…

CVSS 3.1 · [email protected] · Secondary 6.1 MEDIUMCVSS 3.1 · [email protected] · Primary 6.6 MEDIUMCheck source for fixed versionsKEV status unknown

Historical advisory recorded 24 Oct 2026 22:17:22 UTC. Read the latest advisory.

nvd · CVE-2023-39956

Published

Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps that are launched as command line executables are impacted. Specifically this issue can only be exploited if the following conditions are met: 1. The app is launched with an attacker-controlled working directory and 2. The attacker has the ability to write files to that working directory. This makes the risk quite low, in fact normally issues of this kind are considered outside of our threat model as similar to Chromium we exclude Physically Local Attacks but given the ability for this issue to bypass certain protections like ASAR Integrity it is being treated with higher importance. This issue has been fixed in versions:`26.0.0-beta.13`, `25.4.1`, `24.7.1`, `23.3.13`, and `22.3.19`. There are no app side workarounds, users must update to a patched version of Electron.

Read the publisher's advisory

Affected versions, risk and source history

nvd · CVE-2023-39956

Published

Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps that are launched as command line executables are impacted. Specifically this issue can only be exploited if th…

Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps that are launched as command line executables are impacted. Specifically this issue can only be exploited if the following conditions are met: 1. The app is launched with an attacker-controlled working directory and 2. The attacker has the ability to write files to that working directory. This makes the risk quite low, in fact normally issues of this kind are considered outside of our threat model as similar to Chromium we exclude Physically Local Attacks but given the ability for this issue to bypass certain protections like ASAR Integrity it is being treated with higher importance. This issue has been fixed in versions:`26.0.0-beta.13`, `25.4.1`, `24.7.1`, `23.3.13`, and `22.3.19`. There are no app side workarounds, users must update to a patched version of Electron.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-94

Original publisher date fields

published: 2023-09-06T21:15:13.217

lastModified: 2026-06-17T06:13:01.640

21 source CPE criteria · context only
  • cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:alpha1:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:alpha2:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:alpha3:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:alpha4:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:alpha5:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:alpha6:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:alpha7:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:alpha8:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta10:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta11:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta12:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta4:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta5:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta6:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta7:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta8:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:26.0.0:beta9:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
6 Sep 2023 21:15:13 UTC
Source modified
17 Jun 2026 06:13:01 UTC
Saved here
24 Oct 2026 22:17:22 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L

CVSS 3.1 · [email protected] · Primary · 6.6 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current