CVE-2024-21890

Unintended file access via truncated wildcard restrictions

Published Feb 20, 2024 · Updated Apr 30, 2025

Improper wildcard handling in Node.js 20 before 20.11.1 and 21 before 21.6.2 allows local users to access unintended files. The --allow-fs-read and --allow-fs-write handlers treat a nonterminal wildcard as a directory-prefix match and ignore the remaining suffix. Exploitation requires the experimental Permission Model and an operator-supplied wildcard restriction; affected code can read or write files beyond that restriction.

CVSS severity5.0
Medium
EPSS probability0.95%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper wildcard handling in Node.js 20 before 20.11.1 and 21 before 21.6.2 allows local users to access unintended files. The --allow-fs-read and --allow-fs-write handlers treat a nonterminal wildcard as a directory-prefix match and ignore the remaining suffix. Exploitation requires the experimental Permission Model and an operator-supplied wildcard restriction; affected code can read or write files beyond that restriction.

The record

CVE
CVE-2024-21890
Published
Feb 20, 2024
Updated
Apr 30, 2025
Vendor
Node.js
Product
Node.js
Classifications
T1565.001, T1005
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 20, 2024CVE publishedPublication date reported by the CVE source.
  2. Apr 30, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0 <10.*
  2. Affected versionversion=11.0 <11.*
  3. Affected versionversion=12.0 <12.*
  4. Affected versionversion=13.0 <13.*
  5. Affected versionversion=14.0 <14.*
  6. Affected versionversion=15.0 <15.*
  7. Affected versionversion=16.0 <16.*
  8. Affected versionversion=17.0 <17.*
  9. Affected versionversion=19.0 <19.*
  10. Affected versionversion=20.0 <20.11.1
  11. Affected versionversion=21.0 <21.6.2
  12. Affected versionversion=4.0 <4.*
  13. Affected versionversion=5.0 <5.*
  14. Affected versionversion=6.0 <6.*
  15. Affected versionversion=7.0 <7.*
  16. Affected versionversion=8.0 <8.*
  17. Affected versionversion=9.0 <9.*

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Node.js · Node.jsversion=10.0 <10.*; version=11.0 <11.*; version=12.0 <12.*; version=13.0 <13.*; version=14.0 <14.*; version=15.0 <15.*; version=16.0 <16.*; version=17.0 <17.*; version=19.0 <19.*; version=20.0 <20.11.1; version=21.0 <21.6.2; version=4.0 <4.*; version=5.0 <5.*; version=6.0 <6.*; version=7.0 <7.*; version=8.0 <8.*; version=9.0 <9.*

Published CVSS scores

5.0HackerOneCVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
6.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1565.001Stored Data Manipulation
T1005Data from Local System

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo