CVE-2026-126204
Received Received - Intake

MemoryStore Date Mutation in express-rate-limit

Vulnerability report for CVE-2026-126204, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-12

Last updated on: 2026-11-12

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-12
Last Modified
2026-11-12
Generated
2026-11-12
AI Q&A
2026-11-12
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
express-rate-limit express-rate-limit From 8.6.0 (inc) to 8.7.2 (inc)
express-rate-limit express-rate-limit to 8.7.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-682 The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the express-rate-limit library versions 8.6.0 to 8.7.1. The default MemoryStore incorrectly reused a mutable Date object for rate-limiting windows. When skipFailedRequests or skipSuccessfulRequests was enabled, requests finishing after a window reset could improperly decrement the current window's count, allowing a client to bypass rate limits and get up to one extra request in a new window.

Detection Guidance

To detect this vulnerability, check if your system is running express-rate-limit versions 8.6.0 to 8.7.1. Run: npm list express-rate-limit. If the version is within this range, the system is potentially vulnerable.

Impact Analysis

An attacker could exploit this to send slightly more requests than the configured rate limit allows in a short burst. While not enabling sustained abuse, it could reduce the effectiveness of rate limiting, potentially leading to degraded service availability for other users or increased server load.

Mitigation Strategies

Upgrade express-rate-limit to version 8.7.2 or later immediately. Use: npm update express-rate-limit. If upgrading is not possible, consider switching to a different rate-limiting store that does not reuse Date objects.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-126204. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...