critical CVSS 9.1 EPSS <0.1%

CVE-2025-55130·Node.js vulnerability

A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.

Severity
critical
Software
Node.js
Fixed in
25.3.0
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2025-55130 scores 9.1 on CVSS, so a successful attack would be serious — but at <0.1%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

From: 25.0.0

Until: 25.3.0

Fixed in: 25.3.0

How to fix this CVE

Node.js versions 25.0.0 through 25.3.0 contain a critical permission model bypass that allows scripts to escape filesystem restrictions through symlink manipulation. Immediately update to Node.js 25.3.0 or later, or downgrade to a stable LTS version (v22 or v20) if you cannot update immediately. Review your deployment configurations to ensure the permission model flags are being actively used, as this vulnerability only affects systems explicitly leveraging `--allow-fs-read` and `--allow-fs-write` restrictions.

sudo dnf update nodejs

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check the installed Node.js version by running: `node --version` or `nodejs --version` depending on your system configuration
  2. Step 2: Determine if permission model flags are active by examining process startup commands: `ps aux | grep node | grep -E 'allow-fs-(read|write)'`
  3. Step 3: Search application logs for symlink-related path traversal attempts: `grep -r 'EACCES\|Permission denied' /var/log/app/ | grep -i symlink`
  4. Step 4: Verify the patch by confirming the version is 25.3.0 or higher: `node --version` should show v25.3.0+ or a stable LTS version

FAQ

What is CVE-2025-55130?

CVE-2025-55130 is a critical permission model flaw in Node.js that enables attackers to circumvent filesystem access restrictions by crafting relative symlink paths that chain through directories. This allows scripts with limited read/write permissions to access files outside their intended scope, completely undermining the security isolation provided by the permission model.

Is CVE-2025-55130 being actively exploited?

No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities catalog, and no public exploits have been disclosed. However, the simplicity of the exploitation technique (symlink path traversal) means defenders should prioritize patching proactively.

What versions of Node.js are affected by CVE-2025-55130?

Node.js versions 25.0.0 through 25.3.0 are affected. Additionally, the vulnerability impacts v20, v22, and v24 with the permission model enabled, though specific patch versions for those branches vary. Consult the official Node.js security release notes for LTS branch guidance.

How do I check if my server is vulnerable to CVE-2025-55130?

Run `node --version` to see your installed version. If it reports v25.0.0-v25.2.1 and you have process startup commands containing `--allow-fs-read` or `--allow-fs-write`, your system is vulnerable. LTS versions (v22, v20) require checking the patch level against Node.js official advisories.

Does Defensia detect CVE-2025-55130?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Node.js is installed on a monitored server, CVE-2025-55130 will appear in your dashboard with remediation steps.

Related Node.js CVEs

CVE-2026-21636CVSS 10A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when `--permission` is enabled. Even without `--allow-net`, attacker-controlled inputs (such as URLs or socketPath options) can connect to arbitrary local sockets via net, tls, or undici/fetch. This breaks the intended security boundary of the permission model and enables access to privileged local services, potentially leading to privilege escalation, data exposure, or local code execution. * The issue affects users of the Node.js permission model on version v25. In the moment of this vulnerability, network permissions (`--allow-net`) are still in the experimental phase.
CVE-2026-111497CVSS 9.8A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1.2.1.
CVE-2026-48930CVSS 9.8A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2026-21710CVSS 9A flaw in Node.js HTTP request handling causes an uncaught `TypeError` when a request is received with a header named `__proto__` and the application accesses `req.headersDistinct`. When this occurs, `dest["__proto__"]` resolves to `Object.prototype` rather than `undefined`, causing `.push()` to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by `error` event listeners, meaning it cannot be handled without wrapping every `req.headersDistinct` access in a `try/catch`. * This vulnerability affects all Node.js HTTP servers on **20.x, 22.x, 24.x, and v25.x**
CVE-2026-21717CVSS 9A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that causes many such collisions in V8's internal string table, an attacker can significantly degrade performance of the Node.js process. The most common trigger is any endpoint that calls `JSON.parse()` on attacker-controlled input, as JSON parsing automatically internalizes short strings into the affected hash table. This vulnerability affects **20.x, 22.x, 24.x, and 25.x**.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-55130. Free for 1 server.

Get started free