CVE-2026-21714 | Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1 HTTP/2 Server resource consumption
VulDBArchived Mar 30, 2026✓ Full text saved
A vulnerability, which was classified as problematic , was found in Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1 . Affected by this issue is some unknown functionality of the component HTTP2 Server . Such manipulation leads to resource consumption. This vulnerability is documented as CVE-2026-21714 . The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354147 · CVE-2026-21714 · GCVE-0-2026-21714
NODE.JS UP TO 20.20.1/22.22.1/24.14.0/25.8.1 HTTP/2 SERVER RESOURCE CONSUMPTION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.1 $0-$5k 4.42+
Summaryinfo
A vulnerability has been found in Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1 and classified as problematic. This affects an unknown part of the component HTTP2 Server. Performing a manipulation results in resource consumption. This vulnerability is reported as CVE-2026-21714. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.
Detailsinfo
A vulnerability was found in Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1. It has been classified as problematic. This affects an unknown part of the component HTTP2 Server. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability.
It is possible to read the advisory at nodejs.org. This vulnerability is uniquely identified as CVE-2026-21714. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. 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: Resource consumption
CWE: CWE-400 / 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-21714 (🔒)
GCVE (CVE): GCVE-0-2026-21714
GCVE (VulDB): GCVE-100-354147
Entryinfo
Created: 03/30/2026 07:41
Changes: 03/30/2026 07:41 (53)
Complete: 🔍
Cache ID: 99:9EE:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸