CVE-2026-21713
MEDIUMDescription
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**.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 32% of all known CVEs.
References
Related Vulnerabilities
Other CWE-208 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-9494 | Medium | 5.9 | 3.9% | - | Fix |
| CVE-2019-16782 | Medium | 6.3 | 3.7% | - | Fix |
| CVE-2025-53940 | High | 8.5 | 3.2% | - | - |
| CVE-2020-1926 | Medium | 5.9 | 2.5% | - | Fix |
| CVE-2021-43298 | Critical | 9.8 | 2.3% | - | Fix |
| CVE-2024-29995 | High | 8.1 | 1.5% | - | Fix |
Common questions
How do I fix CVE-2026-21713?
Published advisories record a fix for 75 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-21713 being actively exploited?
Not that we know of. CVE-2026-21713 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.39% is the estimated probability that it will be exploited in the next 30 days. That is higher than 32% of all scored CVEs.
How severe is CVE-2026-21713?
CVE-2026-21713 has a CVSS v3 base score of 5.9, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-21713 affect?
Published advisories record a fix for nodejs20 (Amazon), nodejs20-debuginfo (Amazon), nodejs20-debugsource (Amazon), nodejs20-devel (Amazon), and 71 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-21713
Markdown
[](https://tridentstack.com/cve/CVE-2026-21713)HTML
<a href="https://tridentstack.com/cve/CVE-2026-21713"><img src="https://tridentstack.com/cve/badge/CVE-2026-21713.svg" alt="CVE-2026-21713"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-19.