Answer in brief
CVE-2026-133312 records a Medium severity (CVSS 5.3) vulnerability in @fastify/rate-limit vulnerable to failed-login limit bypass via a race condition in the documented flow. The current sources do not mark it as known exploited. The current feed maps @fastify/rate-limit/@fastify/rate-limit (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @fastify/rate-limit/@fastify/rate-limit (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @fastify/rate-limit/@fastify/rate-limitgeneric | >=11.1.0 <11.3.0 | 11.3.0 |
Published upstream
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 21, 2026
@fastify/rate-limit is the rate-limiting plugin for the Fastify web framework. Starting in version 11.1.0, the plugin documented a manual flow for limiting failed login attempts that peeks at the limiter, runs the password check, and consumes a slot only on failure. Because the peek and the consume are two separate store operations with the password check in between, concurrent requests can all pass the peek before any slot is consumed, so in versions 11.1.0 through 11.2.2 a burst of requests runs far more failed attempts than the configured limit, and the sequential path also allowed one attempt more than configured. The default per-request limiter is not affected. The issue is fixed in @fastify/rate-limit 11.3.0, which makes the manual flow atomic by reserving a slot in a single operation and refunding it only on success, and users should upgrade to 11.3.0 or later.
Quoted source text, attributed separately from HOL analysis.