Improper Preservation of Permissions Affecting nodejs:20/nodejs-full-i18n package, versions *


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.01% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-NODEJS-15047326
  • published21 Jan 2026
  • disclosed20 Jan 2026

Introduced: 20 Jan 2026

CVE-2025-55132  (opens in a new tab)
CWE-281  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:9 nodejs:20/nodejs-full-i18n.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:20/nodejs-full-i18n package and not the nodejs:20/nodejs-full-i18n package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1