CVE-2025-55132: 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.
Medium CVSS 5.3
- CVE id
- CVE-2025-55132
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Node.js Runtimes and servers |
>= 20.0.0, < 20.20.0 >= 22.0.0, < 22.22.0 >= 24.0.0, < 24.13.0 >= 25.0.0, < 25.3.0 |
20.20.0, 22.22.0, 24.13.0, 25.3.0 |
How to fix it
Upgrade Node.js to the fixed release of the line you run: 20.20.0, 22.22.0, 24.13.0, 25.3.0.
node --version
- Install the patched Node.js release of your major line (nvm install, or the node image tag) everywhere the app runs and builds.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.