CVE-2025-55130: FS Permissions Bypass

Published Jan 13, 2026
·
Updated

A flaw in Node.js’s Permissions model allows attackers to bypass --allow-fs-read and --allow-fs-write restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise.

Other sources

A flaw in Node.js’s Permissions model allows attackers to bypass --allow-fs-read and --allow-fs-write restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.

— MITRE

Affected Software

10 affected componentsFixes available
npm/node>=20.0.0<26.0.0
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
Node.js Node.js>=20.0.0<20.20.0, >=22.0.0<22.22.0, >=24.0.0<24.13.0, >=25.0.0<25.3.0
20.20.022.22.024.13.025.3.0
Node.js Node.js>=20.0.0<20.20.0
20.20.0
Node.js Node.js>=22.0.0<22.22.0
22.22.0
Node.js Node.js>=24.0.0<24.13.0
24.13.0
Node.js Node.js>=25.0.0<25.3.0
25.3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 20.20.0Fixed in 22.22.0Fixed in 24.13.0Fixed in 25.3.0
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 20.20.0
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 22.22.0
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 24.13.0
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 25.3.0

Event History

Jan 13, 2026
CVE Published
via Node.js·12:00 AM
Data Sourced
via Node.js·12:00 AM
DescriptionSeverityAffected Software
Jan 20, 2026
CVE Published
via MITRE·08:41 PM
Data Sourced
via MITRE·08:41 PM
DescriptionSeverity
Data Sourced
via Red Hat·09:03 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Feb 1, 2026
Exploit Published
via GitHub·05:25 PM

Frequently Asked Questions

1

What is the severity of CVE-2025-55130?

CVE-2025-55130 is considered a significant security vulnerability due to its potential to allow unauthorized access to file system resources.

2

How do I fix CVE-2025-55130?

To remediate CVE-2025-55130, upgrade Node.js to version 26.0.0 or later, where the flaw has been addressed.

3

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

CVE-2025-55130 affects Node.js versions from 20.0.0 to 26.0.0.

4

What are the risks associated with CVE-2025-55130?

The risks include the potential for attackers to bypass file system permission restrictions and access sensitive data.

5

Is CVE-2025-55130 part of a larger vulnerability series?

Yes, CVE-2025-55130 is part of a series of related vulnerabilities in Node.js's permissions model.

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