CVE-2026-21713 Affecting nodejs:24/nodejs-nodemon package, versions <0:3.0.3-1.module_el8.10.0+4061+f8ceeab9


Severity

Recommended
high

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.39% (31st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALMALINUX8-NODEJS-16088919
  • published16 Apr 2026
  • disclosed9 Apr 2026

Introduced: 9 Apr 2026

CVE-2026-21713  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 nodejs:24/nodejs-nodemon to version 0:3.0.3-1.module_el8.10.0+4061+f8ceeab9 or higher.
This issue was patched in ALSA-2026:7670.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:24/nodejs-nodemon package and not the nodejs:24/nodejs-nodemon package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1