Direct Request ('Forced Browsing') Affecting nodejs:20/nodejs 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-RHEL8-NODEJS-15893400
  • published4 Apr 2026
  • disclosed30 Mar 2026

Introduced: 30 Mar 2026

NewCVE-2026-21715  (opens in a new tab)
CWE-425  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 nodejs:20/nodejs.

NVD Description

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

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.

CVSS Base Scores

version 3.1