CVE-2026-21713 | Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1 HMAC Verification crypto_hmac.cc memcmp comparison
VulDBArchived Mar 30, 2026✓ Full text saved
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 . Affected by this vulnerability is the function memcmp of the file crypto_hmac.cc of the component HMAC Verification . This manipulation causes incorrect comparison. This vulnerability is registered as CVE-2026-21713 . Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354146 · CVE-2026-21713 · GCVE-0-2026-21713
NODE.JS UP TO 20.20.1/22.22.1/24.14.0/25.8.1 HMAC VERIFICATION CRYPTO_HMAC.CC MEMCMP COMPARISON
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
3.6 $0-$5k 4.40+
Summaryinfo
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 the function memcmp of the file crypto_hmac.cc of the component HMAC Verification. Such manipulation leads to comparison. This vulnerability is documented as CVE-2026-21713. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Detailsinfo
A vulnerability was found in Node.js up to 20.20.1/22.22.1/24.14.0/25.8.1 and classified as problematic. Affected by this issue is the function memcmp of the file crypto_hmac.cc of the component HMAC Verification. The manipulation with an unknown input leads to a comparison vulnerability. Using CWE to declare the problem leads to CWE-697. The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses. Impacted is integrity.
The advisory is available at nodejs.org. This vulnerability is handled as CVE-2026-21713. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit.
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: 3.7
VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
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: Comparison
CWE: CWE-697
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-21713 (🔒)
GCVE (CVE): GCVE-0-2026-21713
GCVE (VulDB): GCVE-100-354146
Entryinfo
Created: 03/30/2026 07:41
Changes: 03/30/2026 07:41 (54)
Complete: 🔍
Cache ID: 99:BBD:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸