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**.
Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.
Affected products and versions
| Vendor | Product | Versions | |
| nodejs |
node |
20.20.1 – ≤ 20.20.1, 22.22.1 – ≤ 22.22.1, 24.14.0 – ≤ 24.14.0, 25.8.1 – ≤ 25.8.1, 4.0 – < 4.*, 5.0 – < 5.*, 6.0 – < 6.*, 7.0 – < 7.*, 8.0 – < 8.*, 9.0 – < 9.*, 10.0 – < 10.*, 11.0 – < 11.*, 12.0 – < 12.*, 13.0 – < 13.*, 14.0 – < 14.*, 15.0 – < 15.*, 16.0 – < 16.*, 17.0 – < 17.*, 18.0 – < 18.*, 19.0 – < 19.* |
|
| nodejs |
node.js |
≤ 20.20.1 |
|
CPE matches (NVD) (4)
cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:* ≤ 20.20.1cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:* ≥ 22.0.0 ≤ 22.22.1cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:* ≥ 24.0.0 ≤ 24.14.0cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:* ≥ 25.0.0 ≤ 25.8.1