Incorrect count in express-rate-limit MemoryStore allows extra burst requests
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- None · None · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
express-rate-limit from 8.6.0 before 8.7.2 has an incorrect calculation in its built-in MemoryStore when skipFailedRequests or skipSuccessfulRequests is used. A request from an earlier window can decrement the count of the current window after the window has reset (CWE-682). A client that keeps requests in flight across the window boundary can obtain a bounded extra burst of up to one additional configured limit in the new window, without increasing the sustained rate. Stores that return a fresh Date are not affected.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| express-rate-limit | express-rate-limit | 8.6.0 to before 8.7.2 | 8.7.2 | Patch available | CNA |
- express-rate-limit Vendorexpress-rate-limit Affected 8.6.0 to before 8.7.2 Fixed in 8.7.2 Patch available CNA
Remediation
Upgrade express-rate-limit to version 8.7.2, which fixes the issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · CNA express-rate-limit (express-rate-limit) Fixed in 8.7.2
Timeline
- 2026-11-12 Threatist record created from CVE-2026-126204
- 2026-11-13 CISA SSVC decision points changed
References
Other 4
- https://github.com/express-rate-limit/express-rate-limit/security/advisories/GHSA-j3cq-92fq-qg5f
- https://github.com/express-rate-limit/express-rate-limit/pull/707
- https://github.com/express-rate-limit/express-rate-limit/commit/da5b115b97dd903076d37b19437fbd71445e150b
- https://github.com/express-rate-limit/express-rate-limit/releases/tag/v8.7.2
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences