CVE-2025-55132: Medium severity npm/node vulnerability

Published Jan 20, 2026
·
Updated

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.

Affected Software

5 affected components
npm/node
Nodejs Node.js>=20.0.0<20.20.0
Nodejs Node.js>=22.0.0<22.22.0
Nodejs Node.js>=24.0.0<24.13.0
Nodejs Node.js>=25.0.0<25.3.0

Event History

Jan 20, 2026
CVE Published
via MITRE·08:41 PM
Data Sourced
via MITRE·08:41 PM
DescriptionSeverity
Data Sourced
via Red Hat·09:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-55132?

CVE-2025-55132 is classified as a medium severity vulnerability due to its potential for unauthorized modification of file metadata.

2

How do I fix CVE-2025-55132?

To mitigate CVE-2025-55132, update to the latest version of Node.js where the vulnerability is patched.

3

What impact does CVE-2025-55132 have on file management in Node.js?

CVE-2025-55132 allows unauthorized changes to file access and modification timestamps, potentially compromising file integrity.

4

Which versions of Node.js are affected by CVE-2025-55132?

CVE-2025-55132 affects multiple versions of Node.js prior to the security patches released in December 2025.

5

Is there a workaround for CVE-2025-55132 if I cannot update Node.js?

There is no official workaround for CVE-2025-55132, making updating to a patched version the best mitigation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203