Vulnerability DatabaseCVE-2026-133312

CVE-2026-133312: 
JavaScript vulnerability analysis and mitigation

Overview

CVE-2026-133312 is a race condition vulnerability in the @fastify/rate-limit npm package that allows attackers to bypass failed-login attempt limits. It affects versions >= 11.1.0 and < 11.3.0, introduced when the { increment: false } option was added in 11.1.0 and documented as the recommended pattern for limiting failed login attempts. The vulnerability has a CVSS v3.1 base score of 5.3 (Moderate) (GitHub Advisory).

Technical details

The root cause is a Time-of-Check Time-of-Use (TOCTOU) race condition (CWE-367) combined with improper restriction of excessive authentication attempts (CWE-307). The documented login-limiting flow uses two separate store operations: a "peek" (using { increment: false }) to check the current count without consuming a slot, followed by a password check, and then a slot consumption only on failure. Because the peek and consume are non-atomic, concurrent requests can all pass the peek check before any slot is consumed, allowing far more attempts than configured. Additionally, a sequential off-by-one flaw caused the limit to be reported as reached only when the count was strictly above the maximum, permitting one extra attempt even without concurrency (GitHub Advisory).

Impact

An unauthenticated remote attacker can bypass the configured failed-login rate limit, enabling brute-force or credential-stuffing attacks against login endpoints protected by the vulnerable peek-then-consume pattern. In a demonstrated proof-of-concept, a burst of 200 concurrent wrong-password requests against a limiter configured for 5 attempts per minute resulted in all 200 password checks being executed. This primarily impacts confidentiality by exposing authentication mechanisms to exhaustive guessing attacks (GitHub Advisory).

Exploitability

No public exploit code or in-the-wild exploitation has been reported at this time. The vulnerability is straightforward to exploit by any unauthenticated attacker capable of sending concurrent HTTP requests to a targeted login endpoint. The default per-request rate limiter is not affected, limiting the attack surface to applications that explicitly implemented the peek-then-consume pattern as documented. No CISA KEV listing or threat actor attribution is currently known (GitHub Advisory).

Exploitation steps

  1. Reconnaissance: Identify a web application using @fastify/rate-limit versions 11.1.0–11.2.x that protects a login endpoint with the documented { increment: false } peek-then-consume pattern.
  2. Craft concurrent requests: Prepare a large batch of simultaneous HTTP POST requests (e.g., 200 requests) to the login endpoint, each containing an incorrect password for a target account.
  3. Send burst: Use a tool such as curl with parallel execution, ab (Apache Bench), or a custom script to dispatch all requests concurrently before any slot is consumed in the rate-limit store.
  4. Bypass the limiter: Because all requests pass the non-atomic peek check before any slot is recorded, all 200 password checks execute despite the configured limit of (e.g.) 5 per minute.
  5. Brute-force credentials: Repeat with different password candidates across bursts to enumerate valid credentials without triggering the rate limit (GitHub Advisory).

Indicators of compromise

  • Network: A high volume of concurrent HTTP POST requests to a login endpoint originating from the same IP or a small set of IPs within a very short time window.
  • Logs: Application logs showing a large number of failed authentication attempts (e.g., 200+) within a single second or sub-second interval without corresponding rate-limit rejection responses (HTTP 429).
  • Application Behavior: Rate-limit counters in the backing store (e.g., Redis) showing counts far exceeding the configured maximum without corresponding blocked requests being logged.

Mitigation and workarounds

Upgrade to @fastify/rate-limit version 11.3.0 or later, which reworks the login-limiting flow to be atomic using a new { refund: true } option — a slot is reserved in a single store operation and refunded only on successful authentication, eliminating the race window. As a workaround for those unable to upgrade immediately, replace the peek-then-consume pattern with the default per-request limiter on the login route, which performs increment and decision in a single atomic store operation and is not affected by this vulnerability (GitHub Advisory).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

RHEL / CentOS

Unknown

Source: This report was generated using AI

Related JavaScript vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-133867CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/express
NoYesNov 21, 2026
CVE-2026-133250CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/middie
NoYesNov 21, 2026
CVE-2026-133120CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/express
NoYesNov 21, 2026
CVE-2026-133312MEDIUM5.3
  • JavaScript logoJavaScript
  • @fastify/rate-limit
NoYesNov 21, 2026
CVE-2026-133273LOW3.7
  • JavaScript logoJavaScript
  • @fastify/swagger-ui
NoYesNov 21, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management