CVE-2026-106073 Affecting nodejs:24/nodejs-full-i18n package, versions <1:24.22.1-1.module_el8.10.0+4331+0683c9c1


Severity

Recommended
high

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.25% (17th 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-ALMALINUX8-NODEJS-21872717
  • published30 Oct 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-106073  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 nodejs:24/nodejs-full-i18n to version 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 or higher.
This issue was patched in ALSA-2026:92376.

NVD Description

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

A flaw in Node.js Permission Model filesystem enforcement leaves fs.realpathSync() without the required read permission checks. This is an incomplete fix of CVE-2026-21715, which only covered fs.realpathSync.native().

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

This vulnerability affects Node.js 26.x, 24.x, and 22.x.

CVSS Base Scores

version 3.1