# CVE-2025-55130: Path traversal in node

> Attackers can bypass Node.js permission restrictions using crafted symlinks to read or write arbitrary files outside allowed directories.

- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jan 2026
- **Updated:** 15 Jul 2026
- **Also known as:** ALPINE-CVE-2025-55130, AZL-74988, BELL-CVE-2025-55130, BIT-node-2025-55130, BIT-node-min-2025-55130, CLEANSTART-2026-TF09981, DEBIAN-CVE-2025-55130, GHSA-62wc-jj78-f4f6, MINI-5qqx-9hqf-9mf3, MINI-6pg6-fhw5-j696, MINI-7x89-p664-48m2, MINI-7xg6-h23c-h273, MINI-9j2m-r53p-vm3w, MINI-vcrq-2qcc-5gcc, UBUNTU-CVE-2025-55130

## What is CVE-2025-55130?

CVE-2025-55130 is a high-severity path traversal vulnerability in Nodejs Node.js, published on 20 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-281 (Improper Preservation of Permissions), CWE-289 (Authentication Bypass by Alternate Name)

## Which versions are affected by CVE-2025-55130?

2 open source packages ship an affected version, including node and node-min. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | From 20.0.0 | 20.20.0, 22.22.0, 24.13.0, 25.3.0 |
| `node-min` | Bitnami | From 20.0.0 | 20.20.0, 22.22.0, 24.13.0, 25.3.0 |

Products: Nodejs Node.js.

## How do I fix CVE-2025-55130?

Upgrade node to a fixed version for your release line: 20.20.0, 22.22.0, 24.13.0 or 25.3.0.

## Is CVE-2025-55130 being exploited?

There is no known exploitation of CVE-2025-55130 in the wild and no public exploit code.

Public exploit code:

- POC for CVE-2025-55130 (github_poc): https://github.com/scumfrog/CVE-2025-55130

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55130 and fix it if it is affected.

What it is: CVE-2025-55130 is a high-severity path traversal vulnerability in Nodejs Node.js, published on 20 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55130 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected from 20.0.0; fixed in 20.20.0, 22.22.0, 24.13.0, 25.3.0
- node-min (Bitnami): affected from 20.0.0; fixed in 20.20.0, 22.22.0, 24.13.0, 25.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55130/ (Markdown: https://insights.sbomify.com/CVE-2025-55130/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55130
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55130
- OSV: https://osv.dev/vulnerability/CVE-2025-55130

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55130/
Summaries are generated and may contain mistakes; the official description above is the record.