Vigilbase CVEConnect your agent

nodejs node

Not in CISA KEVPublic exploit codeCVE-2025-27210

Not confirmed exploited. 2 of 8 rule sources name it; Cloudflare blocks by default.

Edge rules
2/8
Our test
No exploit yet
CVSS
7.5
EPSS
14.3% Top 3%
Posts, 14d
02026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts
Published
2025-07-18

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.

Ask Vigil

AI · answers from this page
Ask about CVE-2025-27210: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Severity, decoded

CVSS 3.0
High · 7.5 / 10

Exploitable over the network, with no privileges and no user interaction, leading to full loss of confidentiality.

Over the internetNo login neededNo user actionWorks reliablySerious impact
How the score is built8 metrics
  • Attack vectorAn attacker can reach it over the internet; no access to your network needed.
    Network
  • Attack complexityNo special conditions are needed; the attack works reliably.
    Low
  • Privileges requiredNo account or login is needed.
    None
  • User interactionNo one has to click or open anything; the attack works on its own.
    None
  • ScopeThe damage stays within the vulnerable component.
    Unchanged
  • Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.
    High
  • Integrity impactData cannot be changed by the attacker.
    None
  • Availability impactThe component keeps working normally.
    None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CISA's assessmentSSVC, from the CVE record
ExploitationNone

CISA has seen no public exploit and no attacks.

AutomatableYes

Attackers can script the attack end to end and hit many targets at once.

Technical impactPartial

A successful attack gives limited control over the affected software or limited access to its data.

Public exploits

1 found
0 Metasploit1 Exploit-DB0 Scanner template0 GitHub PoCs

Links are to third-party code: never run it outside an isolated lab.

Timeline

  1. 2025-07-16
    Exploit published on Exploit-DB
    NodeJS 24.x - Path Traversal
  2. 2025-07-18
    CVE published
    CVE List
  3. 2025-08-11
    Cloudflare ships a rule
    Node.js - Directory Traversal - CVE:CVE-2025-27210
  4. 2025-08-24
    F5 ships a rule
    Node.js Path Traversal (Parameter)

Social

2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts

No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.

Vendor statements

Quoted
CloudflareWAF Managed Rules1 quoteBlocks by default

First rule 2025-08-11, 24 days after the CVE was published.

2025-08-11New rule…6f1c2d12Default: BlockSource
Node.js - Directory Traversal - CVE:CVE-2025-27210. Previous action: Log. New action: Block. This is a New Detection
AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.

Google CloudCloud Armor preconfigured WAF rulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.

FastlyNext-Gen WAF virtual patchesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

F5Attack signatures (Distributed Cloud WAF)2 quotesRule published

First rule 2025-08-24, 37 days after the CVE was published.

2025-08-24New rule200007100Source
Added: signature 200007100 "Node.js Path Traversal (Parameter)" (Path Traversal, risk High), systems: Node.js. References: CVE-2025-27210.
2025-08-24New rule200007101Source
Added: signature 200007101 "Node.js Path Traversal (Header)" (Path Traversal, risk High), systems: Node.js. References: CVE-2025-27210.
AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.