# CVE-2025-55132: Missing authorization in node

> Attackers can modify file timestamps in read-only directories via futimes(), obscuring activity logs and bypassing permission model restrictions.

- **Severity:** Low 2.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Jan 2026
- **Updated:** 21 Jan 2026
- **Also known as:** ALPINE-CVE-2025-55132, AZL-74982, BELL-CVE-2025-55132, BIT-node-2025-55132, BIT-node-min-2025-55132, CLEANSTART-2026-OM37971, DEBIAN-CVE-2025-55132, GHSA-pm9v-wcw9-xgpv, MINI-284v-3g9f-fr4j, MINI-69m2-fpgf-3c34, MINI-g8rf-7qgc-78x2, MINI-gqmm-qph8-qxrf, MINI-q87x-2q3v-r4cv, MINI-rc62-gfrp-32w2, UBUNTU-CVE-2025-55132

## What is CVE-2025-55132?

CVE-2025-55132 is a low-severity missing authorization vulnerability in Nodejs Node.js, published on 20 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via `futimes()` even when the process has only read permissions. Unlike `utimes()`, `futimes()` does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20,  v22,  v24, and v25.

Weakness: CWE-276 (Incorrect Default Permissions)

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

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-55132?

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-55132 being exploited?

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

## 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-55132 and fix it if it is affected.

What it is: CVE-2025-55132 is a low-severity missing authorization vulnerability in Nodejs Node.js, published on 20 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-55132 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-55132/ (Markdown: https://insights.sbomify.com/CVE-2025-55132/index.md)
```

## Sources

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

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