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: Out-of-package code execution when launched with arbitrary cwd

CVSS 3.1 6.1 MEDIUMEUVD CVSS 3.1 6.1 CVSS 3.1 · [email protected] · Secondary 6.1 MEDIUMCVSS 3.1 · [email protected] · Primary 6.6 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by electron 22.3.19Fixed by electron 23.3.13Fixed by electron 24.7.1Fixed by electron 25.5.0KEV status unknown

cve-program · 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

euvd · EUVD-2023-2462

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

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

osv · GHSA-7x97-j373-85x5

Published

### Impact Apps that are launched as command line executables are impacted. E.g. if your app exposes itself in the path as `myapp --help` Specifically this issue can only be exploited if the following conditions are met: * Your app is launched with an attacker-controlled working directory * 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](https://github.com/electron/electron/security/advisories/GHSA-7x97-j373-85x5#:~:text=Physically%20Local%20Attacks) but given the ability for this issue to bypass certain protections like ASAR Integrity it is being treated with higher importance. Please bear this in mind when reporting similar issues in the future. ### Workarounds There are no app side workarounds, you must update to a patched version of Electron. ### Fixed Versions * `26.0.0-beta.13` * `25.5.0` * `24.7.1` * `23.3.13` * `22.3.19` ### For more information If you have any questions or comments about this advisory, email us at [[email protected]](mailto:[email protected])

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2023-39956

Published

Electron: Out-of-package code execution when launched with arbitrary cwd

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.

Source published
6 Sep 2023 20:09:33 UTC
Source modified
26 Sep 2024 15:17:59 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

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

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

euvd · EUVD-2023-2462

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

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 6, 2023, 8:09:33 PM

dateUpdated: Sep 26, 2024, 3:17:59 PM

1 related source bulletins · separate from aliases

WID-SEC-W-2023-2333: Microsoft Developer Tools: Mehrere Schwachstellen

CVE-2023-39956 · CVE-2023-38155 · CVE-2023-36799 · CVE-2023-36796 · CVE-2023-36794 · CVE-2023-36793 · CVE-2023-36792 · CVE-2023-36788 · CVE-2023-36759 · CVE-2023-36758 · CVE-2023-36742 · CVE-2023-33136

Source published
Sep 6, 2023, 8:09:33 PM (timezone not stated)
Source modified
Sep 26, 2024, 3:17:59 PM (timezone not stated)
Saved here
19 Nov 2026 02:35:46 UTC
Source terms
ENISA EUVD · source terms and attribution apply

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

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

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

osv · GHSA-7x97-j373-85x5

Published

Electron vulnerable to out-of-package code execution when launched with arbitrary cwd

### Impact Apps that are launched as command line executables are impacted. E.g. if your app exposes itself in the path as `myapp --help` Specifically this issue can only be exploited if the following conditions are met: * Your app is launched with an attacker-controlled working directory * 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](https://github.com/electron/electron/security/advisories/GHSA-7x97-j373-85x5#:~:text=Physically%20Local%20Attacks) but given the ability for this issue to bypass certain protections like ASAR Integrity it is being treated with higher importance. Please bear this in mind when reporting similar issues in the future. ### Workarounds There are no app side workarounds, you must update to a patched version of Electron. ### Fixed Versions * `26.0.0-beta.13` * `25.5.0` * `24.7.1` * `23.3.13` * `22.3.19` ### For more information If you have any questions or comments about this advisory, email us at [[email protected]](mailto:[email protected])

Source published
6 Sep 2023 19:51:33 UTC
Source modified
10 Sep 2026 03:49:57 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

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

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

Publisher rating · MODERATE

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