CVE-2025-23084: node
Affects nodeSource GCVE Database
Not known to be exploited · fixed in 23.8.0 : update node when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 1.5% chance of exploitation in 30 days – higher than 75% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 23.8.0, 22.13.1, 20.18.2 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 30 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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
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 26 Oct 2026.
What to do
Upgrade node to 23.8.0, 22.13.1, 20.18.2 or 18.20.6.
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 for this vulnerability. Users should update Node.js to a fixed version outside the affected version ranges. No additional mitigation steps are indicated beyond applying the official fix.
Description
A medium severity vulnerability (CVE-2025-23084) has been identified in Node.js affecting the handling of drive names on Windows. The issue arises because certain Node.js functions, specifically the path.join API, do not treat drive names as special cases. This causes paths assumed to be relative to actually refer to the root directory, potentially leading to incorrect path resolution.