Bug 2572746 (CVE-2026-126204) - CVE-2026-126204 express-rate-limit: express-rate-limit: Rate limit bypass via in-flight request window reset handling
Summary: CVE-2026-126204 express-rate-limit: express-rate-limit: Rate limit bypass via...
Keywords:
Status: NEW
Alias: CVE-2026-126204
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2578340
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-12 18:51 UTC by OSIDB Bzimport
Modified: 2026-11-20 14:49 UTC (History)
28 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-12 18:51:42 UTC
express-rate-limit is a basic rate-limiting middleware for Express. From 8.6.0 until 8.7.2, the built-in MemoryStore returns a Client whose mutable resetTime object is retained by middleware using skipFailedRequests or skipSuccessfulRequests. When a later request resets the client window, MemoryStore.resetClient mutates that same Date, so an earlier request that finishes or disconnects after the reset can pass the stale-window guard and decrement the current window's count. A client able to keep requests in flight across the boundary can obtain a bounded extra burst of up to one additional configured limit in the new window; the behavior does not increase the sustained rate. Stores that return a fresh Date are not affected. This issue is fixed in version 8.7.2.


Note You need to log in before you can comment on or make changes to this bug.