CISA ADP Vulnrichment

Answer in brief

CVE-2026-21715 records a Unknown severity vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps nodejs/node (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Mar 30, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Aug 20, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps nodejs/node (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:a:nodejs:node.js:::::-:::*	Not reported	Not reported

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
nodejs/nodegeneric	20.20.1 \|\| 22.22.1 \|\| 24.14.0 \|\| 25.8.1 \|\| >=4.0 <4.* \|\| >=5.0 <5.* \|\| >=6.0 <6.* \|\| >=7.0 <7.* \|\| >=8.0 <8.* \|\| >=9.0 <9.* \|\| >=10.0 <10.* \|\| >=11.0 <11.* \|\| >=12.0 <12.* \|\| >=13.0 <13.* \|\| >=14.0 <14.* \|\| >=15.0 <15.* \|\| >=16.0 <16.* \|\| >=17.0 <17.* \|\| >=18.0 <18.* \|\| >=19.0 <19.*	4., 5., 6., 7., 8., 9., 10., 11., 12., 13., 14., 15., 16., 17., 18., 19.

Recommended response

Check inventory. Check lockfiles and deployed manifests for nodejs/node.
Review the reported fix. Update nodejs/node to 4.* if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Mar 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 20, 2026

Sources and claim methodology

Source referencenodejs.org

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.