CVE-2026-21710 | Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1 req.headersDistinct denial of service
VulDBArchived Mar 30, 2026✓ Full text saved
A vulnerability described as problematic has been identified in Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1 . This affects an unknown function. Executing a manipulation of the argument req.headersDistinct can lead to denial of service. This vulnerability is tracked as CVE-2026-21710 . The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354143 · CVE-2026-21710 · GCVE-0-2026-21710
NODE.JS UP TO 20.20.1/22.22.1/24.14.0/25.8.1 REQ.HEADERSDISTINCT DENIAL OF SERVICE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.1 $0-$5k 4.24+
Summaryinfo
A vulnerability classified as problematic has been found in Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1. This impacts an unknown function. The manipulation of the argument req.headersDistinct leads to denial of service. This vulnerability is listed as CVE-2026-21710. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.
Detailsinfo
A vulnerability, which was classified as problematic, has been found in Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1. This issue affects some unknown processing. The manipulation of the argument req.headersDistinct with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability.
It is possible to read the advisory at nodejs.org. The identification of this vulnerability is CVE-2026-21710. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Upgrading to version 20.20.2, 22.22.2, 24.14.1 or 25.8.2 eliminates this vulnerability. The upgrade is hosted for download at nodejs.org.
Productinfo
Type
JavaScript Library
Name
Node.js
Version
20.20.0
20.20.1
22.22.0
22.22.1
24.0
24.1
24.2
24.3
24.4
24.5
24.6
24.7
24.8
24.9
24.10
24.11
24.12
24.13
24.14.0
25.8.0
25.8.1
License
open-source
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Denial of service
CWE: CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Node.js 20.20.2/22.22.2/24.14.1/25.8.2
Timelineinfo
03/30/2026 Advisory disclosed
03/30/2026 +0 days VulDB entry created
03/30/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: nodejs.org
Status: Confirmed
CVE: CVE-2026-21710 (🔒)
GCVE (CVE): GCVE-0-2026-21710
GCVE (VulDB): GCVE-100-354143
Entryinfo
Created: 03/30/2026 07:41
Changes: 03/30/2026 07:41 (53)
Complete: 🔍
Cache ID: 99:0F5:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸