CVE-2023-32003

`fs.mkdtemp()` and `fs.mkdtempSync()` can be used to bypass the permission model check using a path traversal attack. This flaw arises from a missing check in the fs.mkdtemp() API and the impact is a malicious actor could create an arbitrary directory. This vulnerability affects all users using the experimental permission model in Node.js 20. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

Published: 2023-08-15 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-32003 is rated Moderate Risk (43.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.05%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-32003

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.07% 1.05% +0.98%
2 2026-03-04 0.04% 0.07% +0.03%
3 2026-03-01 — 0.04% —

Full EPSS history (22 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-32003

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2023-32003

OS Trackers for CVE-2023-32003

vendor priority summary link
alpine — CVE-2023-32003: 1 source package rows (nodejs); 162 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 162. https://security.alpinelinux.org/vuln/CVE-2023-32003
debian unimportant CVE-2023-32003 unimportant priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-32003
gentoo low CVE-2023-32003: 1 GLSA(s) (202405-29), 1 atom(s) (net-libs/nodejs); latest impact low. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2023-32003
redhat low — https://access.redhat.com/security/cve/CVE-2023-32003
suse medium CVE-2023-32003 severity moderate: SUSE including 37 source package names (corepack20-20.5.1-1.1, nodejs10, …), 207 product×package rows across 20 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 7.1, … (20 product lines)): Known Not Affected 202, Fixed 5. https://www.suse.com/security/cve/CVE-2023-32003/
ubuntu medium CVE-2023-32003 medium priority: Ubuntu including 1 source packages (nodejs), 9 status rows across 9 suites (bionic, focal, jammy, lunar, mantic, noble, trusty, upstream, xenial): not-affected 8, ignored 1. https://ubuntu.com/security/CVE-2023-32003

Affected software / configurations for CVE-2023-32003

Vendor Product Version Raw CPE
nodejs node.js >= 20.0.0, <= 20.5.0 cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
fedoraproject fedora 37 cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*
fedoraproject fedora 38 cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*

References for CVE-2023-32003

cvelogic Threat Intelligence