CVE-2025-55132

File timestamp modification via unchecked fs.futimes permission

Published Jan 20, 2026 · Updated Jan 20, 2026

Permission bypass in Node.js 20, 22, 24, and 25 allows attackers to alter file timestamps through fs.futimes() under read-only access. The fs.futimes() path accepts an open file descriptor and updates access and modification times without enforcing the write-permission check applied by fs.utimes(). The process must use the opt-in permission model and hold a readable file descriptor; the bypass changes metadata only, enabling timestamp obfuscation without file-content modification.

CVSS severity5.3
Medium
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Permission bypass in Node.js 20, 22, 24, and 25 allows attackers to alter file timestamps through fs.futimes() under read-only access. The fs.futimes() path accepts an open file descriptor and updates access and modification times without enforcing the write-permission check applied by fs.utimes(). The process must use the opt-in permission model and hold a readable file descriptor; the bypass changes metadata only, enabling timestamp obfuscation without file-content modification.

The record

CVE
CVE-2025-55132
Published
Jan 20, 2026
Updated
Jan 20, 2026
Vendor
Node.js
Product
Node.js
Classifications
CWE-276, T1070.006
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Jan 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=20.19.6 <=20.19.6
  2. Affected versionversion=22.21.1 <=22.21.1
  3. Affected versionversion=24.12.0 <=24.12.0
  4. Affected versionversion=25.2.1 <=25.2.1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

Node.js · Node.jsversion=20.19.6 <=20.19.6; version=22.21.1 <=22.21.1; version=24.12.0 <=24.12.0; version=25.2.1 <=25.2.1

Published CVSS scores

3.1Amazon LinuxCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
5.3NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
2.8HackerOneCVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-276Incorrect Default Permissions
T1070.006Timestomp

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo