CVE-2026-21715: Permission Model Bypass in realpathSync.native Allows File Existence Disclosure

Published Mar 24, 2026
·
Updated

A flaw in Node.js Permission Model filesystem enforcement leaves fs.realpathSync.native() without the required read permission checks, while all comparable filesystem functions correctly enforce them.

As a result, code running under --permission with restricted --allow-fs-read can still use fs.realpathSync.native() to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories.

This vulnerability affects 20.x, 22.x, 24.x, and 25.x processes using the Permission Model where --allow-fs-read is intentionally restricted.

Other sources

A flaw in Node.js Permission Model filesystem enforcement leaves fs.realpathSync.native() without the required read permission checks, while all comparable filesystem functions correctly enforce them.

As a result, code running under --permission with restricted --allow-fs-read can still use fs.realpathSync.native() to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories.

— Node.Js

Affected Software

12 affected componentsFixes available
Node.js Node.js>=20.0.0<21.0.0, >=22.0.0<23.0.0, >=24.0.0<25.0.0, >=25.0.0<26.0.0
Microsoft azl3 nodejs 20.14.0-14
Microsoft azl3 nodejs24 24.13.0-3
Nodejs Node.js<=20.20.1
Nodejs Node.js>=22.0.0<=22.22.1
Nodejs Node.js>=24.0.0<=24.14.0
Nodejs Node.js>=25.0.0<=25.8.1
Node.js Node.js>=20.0.0<20.20.2, >=22.0.0<22.22.2, >=24.0.0<24.14.1, >=25.0.0<25.8.2
20.20.222.22.224.14.125.8.2
Node.js Node.js>=20.0.0<20.20.2
20.20.2
Node.js Node.js>=22.0.0<22.22.2
22.22.2
Node.js Node.js>=24.0.0<24.14.1
24.14.1
Node.js Node.js>=25.0.0<25.8.2
25.8.2

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.2Fixed in 22.22.2Fixed in 24.14.1Fixed in 25.8.2
  2. Upgrade

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

    Fixed in 20.20.2
  3. Upgrade

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

    Fixed in 22.22.2
  4. Upgrade

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

    Fixed in 24.14.1
  5. Upgrade

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

    Fixed in 25.8.2

Event History

Mar 24, 2026
CVE Published
via Node.js·03:00 AM
Data Sourced
via Node.js·03:00 AM
DescriptionSeverityAffected Software
Mar 30, 2026
CVE Published
via MITRE·07:07 PM
Data Sourced
via MITRE·07:07 PM
DescriptionSeverity
Data Sourced
via Red Hat·08:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeaknessAffected Software
Apr 1, 2026
Data Sourced
via Microsoft·08:18 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-21715?

CVE-2026-21715 has a high severity due to the lack of required read permission checks in the `fs.realpathSync.native()` function.

2

How do I fix CVE-2026-21715?

To fix CVE-2026-21715, update to the latest version of Node.js that addresses this vulnerability.

3

What software versions are affected by CVE-2026-21715?

CVE-2026-21715 affects Node.js versions from 20.0.0 to 21.0.0, 22.0.0 to 23.0.0, 24.0.0 to 25.0.0, and 25.0.0 to 26.0.0.

4

Can CVE-2026-21715 be exploited?

Yes, CVE-2026-21715 can be exploited by running code with the `--permission` flag, allowing unauthorized filesystem read operations.

5

What environments are most at risk from CVE-2026-21715?

Environments running Node.js applications with restricted filesystem permissions using `--allow-fs-read` are at the highest risk from CVE-2026-21715.

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