CVE-2025-27210 nodejs · node

node Improper Limitation of a Pathname to a Restricted Directory Vulnerability

Vulnerability at a glance

Severity, exploitation likelihood & attack requirements

CVSS v3.0 severity
7.5High
EPSS · exploitation likelihood
14.338% Probability within 30 daysPercentile 96.7
EPSS trend
UnavailableNo comparable history
Known exploitation
Not in KEV CISA KEV catalog Absence does not establish safety
Attack vector
NetworkRemotely reachable
Attack complexity
LowFewer obstacles to exploitation
Privileges required
NoneNo authentication required
User interaction
NoneNo user action needed
Exploit availability & maturity
Not scored Availability not established No explicit exploit maturity assessment View exploit evidence
How to read the colors & trend
Higher exposureElevatedModerateLower exposureUnknown / unassessed

CVSS colors follow its reported severity. Attack-factor colors describe each requirement, not an overall risk rating. Gray also covers absence from KEV; absence does not establish safety.

EPSS display bands: below 1% blue, 1–10% amber, 10–50% orange, 50% and above red. These are presentation bands, not FIRST severity categories. The trend compares daily EPSS probabilities, not percentile ranks; “pp” means percentage points. The sparkline shows relative movement, with its vertical scale fitted to the observed scores.

Already protected by existing Atomicorp rules No new CVE-specific rule required.

Atomicorp ModSecurity protection

Protected by Atomicorp rules

Atomicorp ModSecurity rules block attacks exploiting this vulnerability. Keep your rules current.

By targeting underlying attack techniques and CWE weakness classes, existing rules can protect against newly disclosed vulnerabilities. Rule changes are regression-tested against attack and false-positive corpora.

1 rule identified Verified 2026-11-22 View rules & research details →

WAF protection does not change the CVSS or EPSS score. Keep your software patched and your Atomicorp rules current.

CISA SSVC assessment

CISA ADP · Assessed 2025-07-21 · SSVC 2.0.3

Exploitation
None reported
Automatable
Yes
Technical Impact
Partial

Stakeholder-Specific Vulnerability Categorization records CISA’s assessment of exploitation, automation, and technical impact. “None reported” reflects the assessment date; it does not establish that no exploit exists. View SSVC source details.

On this page

CVE Details

Technical vulnerability details · CVSS assessments, exploit evidence & CPE data

CVSS assessments

CVSS v3.0 · support@hackerone.com

  • Base score: 7.5
  • Base severity: HIGH
  • Exploitability subscore: 3.9
  • Impact subscore: 3.6
  • Assessment type: Secondary
  • Source identifier: support@hackerone.com
  • Full vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: None
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: High
    • Integrity impact: None
    • Availability impact: None
  • Exploit maturity: Not scored

Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.

Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)

CISA SSVC assessments

These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.

  • Provider: CISA ADP
  • Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
  • SSVC version: 2.0.3
  • Role: CISA Coordinator
  • Assessment timestamp: 2025-07-21T17:11:02.439546Z
  • Exploitation: none
  • Automatable: yes
  • Technical Impact: partial
  • Source: CISA ADP in the CVE record (opens in a new tab)

Vulnerable CPE configurations

No vulnerable CPE configurations are supplied in the current NVD record. See the affected-product information and vendor guidance on this page.

Vulnerability Description

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.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340034 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: nodejs node versions earlier than 20.19.4.
    • Affected versions: nodejs node versions earlier than 22.17.1.
    • Affected versions: nodejs node versions earlier than 24.4.1.
    • Affected versions: nodejs versions earlier than 4.*.
    • Affected versions: nodejs versions earlier than 5.*.
    • Affected versions: nodejs versions earlier than 6.*.
    • Affected versions: nodejs versions earlier than 7.*.
    • Affected versions: nodejs versions earlier than 8.*.
    • Affected versions: nodejs versions earlier than 9.*.
    • Affected versions: nodejs versions earlier than 10.*.
    • Affected versions: nodejs versions earlier than 11.*.
    • Affected versions: nodejs versions earlier than 12.*.
    • Affected versions: nodejs versions earlier than 13.*.
    • Affected versions: nodejs versions earlier than 14.*.
    • Affected versions: nodejs versions earlier than 15.*.
    • Affected versions: nodejs versions earlier than 16.*.
    • Affected versions: nodejs versions earlier than 17.*.
    • Affected versions: nodejs versions earlier than 18.*.
    • Affected versions: nodejs versions earlier than 19.*.
    • Recommended upgrade: Upgrade nodejs node to 20.19.4 or later.
    • Recommended upgrade: Upgrade nodejs node to 22.17.1 or later.
    • Recommended upgrade: Upgrade nodejs node to 24.4.1 or later.
    • Recommended upgrade: Upgrade nodejs to 4.* or later.
    • Recommended upgrade: Upgrade nodejs to 5.* or later.
    • Recommended upgrade: Upgrade nodejs to 6.* or later.
    • Recommended upgrade: Upgrade nodejs to 7.* or later.
    • Recommended upgrade: Upgrade nodejs to 8.* or later.
    • Recommended upgrade: Upgrade nodejs to 9.* or later.
    • Recommended upgrade: Upgrade nodejs to 10.* or later.
    • Recommended upgrade: Upgrade nodejs to 11.* or later.
    • Recommended upgrade: Upgrade nodejs to 12.* or later.
    • Recommended upgrade: Upgrade nodejs to 13.* or later.
    • Recommended upgrade: Upgrade nodejs to 14.* or later.
    • Recommended upgrade: Upgrade nodejs to 15.* or later.
    • Recommended upgrade: Upgrade nodejs to 16.* or later.
    • Recommended upgrade: Upgrade nodejs to 17.* or later.
    • Recommended upgrade: Upgrade nodejs to 18.* or later.
    • Recommended upgrade: Upgrade nodejs to 19.* or later.
  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .