Skip to main content
VulnerabilityPublished Updated

CVE-2025-55132: Node.js's permission model

Affects nodeSource GCVE Database

0
Authoritative record:CVE-2025-55132· Low 2.8

Not known to be exploited · CVSS 2.8 Low · fixed in 25.3.0 : update node when convenient.

Data as of 26 Oct 2026, 10:12 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.
Patch
Available – fixed in 25.3.0, 24.13.0, 22.22.0 +1
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 26 Oct 2026.

What to do

Upgrade node to 25.3.0, 24.13.0, 22.22.0 or 20.20.0.

Affected software

ProductAffectedFixed in
Bitnaminodepkg:bitnami/nodeOther threatsAffected
  • >=20.0.0 <20.20.0
  • >=21.0.0 <22.22.0
  • >=23.0.0 <24.13.0
  • >=25.0.0 <25.3.0
Fixed in
  • 20.20.0
  • 22.22.0
  • 24.13.0
  • 25.3.0

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

AI-suggested

A patch is available for this vulnerability. Users should update affected Node.js versions to the fixed releases beyond the specified affected version ranges. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in Node.js's permission model allows modification of a file's access and modification timestamps via the futimes() function even when the process only has read permissions. This occurs because futimes() does not enforce the expected write-permission checks, unlike utimes(). This flaw affects Node.js versions 20.0.0 up to but not including 20.20.0, 21.0.0 up to but not including 22.22.0, 23.0.0 up to but not including 24.13.0, and 25.0.0 up to but not including 25.3.0. The vulnerability could be used to obscure file activity by altering timestamps, impacting the reliability of logs. A patch is available to address this issue.

References

Community reviews

Loading reviews…