CVE-2026-126204: express-rate-limit skipFailedRequests / skipSuccessfulRequests: with the default MemoryStore, a request from an earlier window is still un-counted from the current window

Published Nov 12, 2026
·
Updated

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.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade express-rate-limit to a version that resolves this vulnerability.

    Fixed in 8.7.2

Event History

Nov 12, 2026
CVE Published
via MITRE·06:47 PM
Data Sourced
via MITRE·06:47 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Deployments using express-rate-limit versions 8.6.0 through 8.7.1 with the built-in MemoryStore and either skipFailedRequests or skipSuccessfulRequests enabled are affected. Stores that return a fresh Date are not affected.

2

What does an attacker need to do to exploit this behavior?

An attacker must be able to keep requests in flight across a rate-limit window boundary, then have an earlier request finish or disconnect after a later request resets the client window. No privileges or user interaction are required.

3

What is the practical impact on rate limiting?

A client can receive a bounded extra burst of up to one additional configured limit in the new window. The issue does not increase the sustained request rate.

4

How can this be remediated?

Upgrade express-rate-limit to version 8.7.2, which fixes the issue. If upgrading is not immediately possible, avoid the affected built-in MemoryStore configuration by using a store that returns a fresh Date.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203