Skip to main content
CVE-2025-55132VulnerabilityPublished

CVE-2025-55132: nodejs node · Vulnerability

Affects nodejs nodeSource CVE Database V5

0

Not known to be exploited · CVSS 2.8 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score
2.8Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=20.19.6 <=20.19.6
  • >=22.21.1 <=22.21.1
  • >=24.12.0 <=24.12.0
  • >=25.2.1 <=25.2.1
Fixed in–
npmnodepkg:npm/nodeOther threatsAffected
  • =20.19.6
  • =22.21.1
  • =24.12.0
  • =25.2.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor Node.js vendor announcements and apply official patches promptly once available. 2. Implement file integrity monitoring solutions that track unexpected changes to file metadata, including timestamps, to detect suspicious activity. 3. Restrict local access to systems running affected Node.js versions to trusted users only, minimizing the risk of exploitation by low-privilege users. 4. Enhance logging and auditing mechanisms to include additional contextual information beyond timestamps, such as file hashes or access logs, to improve detection of tampering. 5. Consider using containerization or sandboxing to limit the scope of processes that can invoke futimes() on critical files. 6. Educate system administrators and security teams about this vulnerability to increase awareness and readiness for incident response. 7. Review and tighten file system permissions and access controls to reduce unnecessary read permissions on sensitive directories.

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.

References

Community reviews

Loading reviews…