NVD / CVE Program· CNA hackerone

CVE-2025-23084: A vulnerability has been identified in Node.js, specifically affecting the handling of drive names in the Windows environment.

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.7% of all records.
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: NodeJS Node 10.*, 11.*, 12.*.

Low priority for now. Upgrade to NodeJS Node 10.*, 11.*, 12.* or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A vulnerability has been identified in Node.js, specifically affecting the handling of drive names in the Windows environment. Certain Node.js functions do not treat drive names as special on Windows. As a result, although Node.js assumes a relative path, it actually refers to the root directory. On Windows, a path that does not start with the file separator is treated as relative to the current directory. This vulnerability affects Windows users of `path.join` API.

MediumCVSS 5.5 · v3.1—No exploit Fix available

Path traversal

BDU:2025-10621

Published: Jan 28, 2025
Updated: Jun 17, 2026
EPSS: 1.5% · 75th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 5.5
CNA · hackerone: 5.6; 0.1 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
nodejs	node.js	cpe:2.3:a:nodejs:node.js
microsoft	windows	cpe:2.3:o:microsoft:windows

Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

nodejs node.js18.0 and later · before 18.20.6
nodejs node.js20.0 and later · before 20.18.2
nodejs node.js22.0 and later · before 22.13.1
nodejs node.js23.0 and later · before 23.6.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

NodeJS Node
- 4.0 and later · before 4.*affected · semver
- 5.0 and later · before 5.*affected · semver
- 6.0 and later · before 6.*affected · semver
- 7.0 and later · before 7.*affected · semver
- 8.0 and later · before 8.*affected · semver
- 9.0 and later · before 9.*affected · semver
- 10.0 and later · before 10.*affected · semver
- 11.0 and later · before 11.*affected · semver
- 12.0 and later · before 12.*affected · semver
- 13.0 and later · before 13.*affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.22	nodejs	before 22.13.1-r0	22.13.1-r0

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed
56Plan
CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an
53Plan
CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c
50Plan

Published before and after this one in the same product

← EarlierCVE-2024-21896Feb 19, 2024 · The permission model protects itself against path traversal attacks by calling path.resolve() on any paths given by the user.
39Monitor
← EarlierCVE-2024-22019Feb 19, 2024 · A vulnerability in Node.js HTTP servers allows an attacker to send a specially crafted HTTP request with chunked encoding, leading to resour
31Monitor
Later →CVE-2025-55130Jan 20, 2026 · A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relativ
37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
NodeJS Node	10.*	Vendor (CNA)
NodeJS Node	11.*	Vendor (CNA)
NodeJS Node	12.*	Vendor (CNA)
NodeJS Node	13.*	Vendor (CNA)
NodeJS Node	14.*	Vendor (CNA)
NodeJS Node	15.*	Vendor (CNA)
NodeJS Node	16.*	Vendor (CNA)
NodeJS Node	17.*	Vendor (CNA)
NodeJS Node	18.20.6	Vendor (CNA)
NodeJS Node	19.*	Vendor (CNA)
NodeJS Node	20.18.2	Vendor (CNA)
NodeJS Node	21.*	Vendor (CNA)
NodeJS Node	22.13.1	Vendor (CNA)
NodeJS Node	23.6.1	Vendor (CNA)
NodeJS Node	4.*	Vendor (CNA)
NodeJS Node	5.*	Vendor (CNA)
NodeJS Node	6.*	Vendor (CNA)
NodeJS Node	7.*	Vendor (CNA)
NodeJS Node	8.*	Vendor (CNA)
NodeJS Node	9.*	Vendor (CNA)
alpine:nodejs	22.13.1-r0 · Alpine:v3.22	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2023-39332468 days apartVarious `node:fs` functions allow specifying paths as either strings or `Uint8Array` objects.
40Plan
CVE-2023-32004532 days apartA vulnerability has been discovered in Node.js version 20, specifically within the experimental permission model.
36Monitor
CVE-2024-21891344 days apartNode.js depends on multiple built-in utility functions to normalize paths provided to node:fs functions, which can be overwitten with user-d
35Monitor
CVE-2023-32558504 days apartThe use of the deprecated API `process.binding()` can bypass the permission model through path traversal.
31Monitor
CVE-2023-39331468 days apartA previously disclosed vulnerability (CVE-2023-30584) was patched insufficiently in commit 205f1e6.
30Monitor
CVE-2023-32003532 days apart`fs.mkdtemp()` and `fs.mkdtempSync()` can be used to bypass the permission model check using a path traversal attack.
21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

Node.jsHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

nodejs.org/en/blog/vulnerability/january-2025-security-releases

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records