NVD / CVE Program· CNA hackerone

CVE-2025-27210: An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.

Noroxi assessment

Priority: Monitor (action score 34/100)

Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 14.3% (FIRST EPSS); higher than 96.6% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: nodejs node 20.19.4, 22.17.1, 24.4.1; nodejs nodejs 10.*, 11.*, 12.*.

Low priority for now. Upgrade to nodejs node 20.19.4, 22.17.1, 24.4.1; nodejs nodejs 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

An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX. This vulnerability affects Windows users of `path.join` API.

HighCVSS 7.5 · v3.0—Proof of concept Fix available

BDU:2025-09382

Published: Jul 18, 2025
Updated: Jun 17, 2026
EPSS: 14.3% · 96th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 4 / 30 · 14.3%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · hackerone: 7.5; NVD has not scored this yet; the score shown is the CNA’s.

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
Proof of concept exists, no weaponized module
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.

—

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

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
- 20.0.0 and later · before 20.19.4affected · semver
- 22.0.0 and later · before 22.17.1affected · semver
- 24.0.0 and later · before 24.4.1affected · semver
nodejs nodejs
- 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

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 f
58Plan
CVE-2024-27980Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject a
32Monitor
CVE-2024-36138Bypass incomplete fix of CVE-2024-27980, that arises from improper handling of batch files with all possible extensions on Windows via child
32Monitor

Published before and after this one in the same product

← EarlierCVE-2025-23167May 18, 2025 · A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`.
26Monitor
← EarlierCVE-2025-27209Jul 18, 2025 · The V8 release used in Node.js v24.0.0 has changed how string hashes are computed using rapidhash.
30Monitor
Later →CVE-2025-55131Jan 20, 2026 · A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module wit
29Monitor

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	20.19.4	Vendor (CNA)
nodejs node	22.17.1	Vendor (CNA)
nodejs node	24.4.1	Vendor (CNA)
nodejs nodejs	10.*	Vendor (CNA)
nodejs nodejs	11.*	Vendor (CNA)
nodejs nodejs	12.*	Vendor (CNA)
nodejs nodejs	13.*	Vendor (CNA)
nodejs nodejs	14.*	Vendor (CNA)
nodejs nodejs	15.*	Vendor (CNA)
nodejs nodejs	16.*	Vendor (CNA)
nodejs nodejs	17.*	Vendor (CNA)
nodejs nodejs	18.*	Vendor (CNA)
nodejs nodejs	19.*	Vendor (CNA)
nodejs nodejs	4.*	Vendor (CNA)
nodejs nodejs	5.*	Vendor (CNA)
nodejs nodejs	6.*	Vendor (CNA)
nodejs nodejs	7.*	Vendor (CNA)
nodejs nodejs	8.*	Vendor (CNA)
nodejs nodejs	9.*	Vendor (CNA)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Exploit-DB entry ×1
Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Exploit-DB entry	remote	2025-07-16
Proof-of-concept repository on GitHub	stars:2	2025-07-16
Proof-of-concept repository on GitHub	stars:0	2025-09-16

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.

First PoCJul 16, 2025-3 d
PublishedJul 18, 2025
TodayNov 6, 2026+475 d

EPSS, last 120 days-1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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-30584314 days apartA vulnerability has been discovered in Node.js version 20, specifically within the experimental permission model.
30Monitor
CVE-2024-37372191 days apartThe Permission Model assumes that any path starting with two backslashes \ has a four-character prefix that can be ignored, which is not alw
14Monitor

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

Anyone who can reach it over the internet can trigger it.
No account or password is required.
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: Network
Attack complexity: Low
Privileges required: None
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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

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/july-2025-security-releases

Show all references (1 more)

www.openwall.com/lists/oss-security/2025/07/22/2

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

All records