CVE-2026-21713 Information disclosure in node

What is CVE-2026-21713?

CVE-2026-21713 is a medium-severity vulnerability in Nodejs Node.js, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

A flaw in Node.js HMAC verification uses a non-constant-time comparison when validating user-provided signatures, potentially leaking timing information proportional to the number of matching bytes. Under certain threat models where high-resolution timing measurements are possible, this behavior could be exploited as a timing oracle to infer HMAC values. Node.js already provides timing-safe comparison primitives used elsewhere in the codebase, indicating this is an oversight rather than an intentional design decision. This vulnerability affects **20.x, 22.x, 24.x, and 25.x**.

Weakness: CWE-208

Which versions are affected by CVE-2026-21713?

2 open source packages ship an affected version, including node and node-min. It affects 1 product.

Products include Nodejs Node.js.

How do I fix CVE-2026-21713?

Upgrade node to a fixed version for your release line: 20.20.2, 22.22.2, 24.14.1 or 25.8.2.

Is CVE-2026-21713 being exploited?

There is no known exploitation of CVE-2026-21713 in the wild and no public exploit code.

Other vulnerabilities in Nodejs Node.js

• CVE-2023-32002 Security feature bypass in Node Critical 9.8
• CVE-2016-6303 Integer overflow in n/a Critical 9.8
• CVE-2017-15896 Security feature bypass in Node.js Critical 9.1
• CVE-2018-7160 Server-side request forgery in Node.js High 8.8
• CVE-2018-12120 Misconfiguration in Node.js High 8.1

All Nodejs Node.js vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as ALPINE-CVE-2026-21713, AZL-81242, AZL-81248, BELL-CVE-2026-21713, BIT-node-2026-21713, BIT-node-min-2026-21713 and 11 more.