CVE-2025-27210: An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows
Affects nodeSource GCVE Database
Mentioned vulnerabilities
Public exploit available (Exploit-DB) · CVSS 7.5 High · fixed in 24.4.1 : patch node as a priority.
Data as of 4 Nov 2026, 18:27 UTC
Thin evidence
One scorer or none| CNA (hackerone) | CVSS 3.0 | 7.5 |
|---|
- Patch
- Available – fixed in 24.4.1, 22.17.1, 20.19.4
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 18 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by HackerOne
, 148 days before disclosure
First Exploit-DB entry (opens in a new tab)
NodeJS 24.x - Path Traversal
, 2 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 7 minutes after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade node to 24.4.1, 22.17.1 or 20.19.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnaminodepkg:bitnami/nodeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and users should upgrade to Node.js versions 20.19.4, 22.17.1, or 24.4.1 or later to remediate this vulnerability. No other mitigation steps are indicated.
Description
An incomplete fix was found for CVE-2025-23084 in Node.js affecting the Windows-specific device names such as CON, PRN, and AUX when using the path.join API. This vulnerability impacts Windows users of Node.js versions prior to the fixed releases. The issue is addressed in Node.js versions 20.19.4, 22.17.1, and 24.4.1.