CVE-2026-106071 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.2% (10th 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-21872662
  • published30 Oct 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-106071  (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 can grant access to paths that do not match a wildcard --allow-fs-read or --allow-fs-write rule.

When the requested path is shorter than the prefix of a wildcard grant, the radix tree lookup stops comparing early and treats the path as a match. For example, --allow-fs-read=/etc/passwd.* also allows reading /etc/passwd. This requires the wildcard grant to sit directly under the root of the permission tree, for example when it is the only grant for that scope. This is a different root cause from CVE-2026-58043.

This vulnerability affects Node.js 26.x.

CVSS Base Scores

version 3.1