{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-126204 in the wild and no public exploit code.","exposure":"An affected version is only exploitable if your software calls MemoryStore.resetClient. Many projects that include it are not exposed.","fix":"No fix has been published for CVE-2026-126204 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-126204 is a low-severity security feature bypass vulnerability in express-rate-limit, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-126204 and fix it if it is affected.\n\nWhat it is: CVE-2026-126204 is a low-severity security feature bypass vulnerability in express-rate-limit, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-126204 in the wild and no public exploit code.\nExposure: An affected version is only exploitable if your software calls MemoryStore.resetClient. Many projects that include it are not exposed.\n\nAffected product: express-rate-limit. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n   If an affected version is present, also search the code for calls to MemoryStore.resetClient and report whether any exist.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-126204/ (Markdown: https://insights.sbomify.com/CVE-2026-126204/index.md)","id":"CVE-2026-126204","markdown":"https://insights.sbomify.com/CVE-2026-126204/index.md","name":"CVE-2026-126204","record":{"aliases":["GHSA-j3cq-92fq-qg5f"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Node.js rate limiting middleware","requires_auth":"none","requires_specific_call":true,"summary":"Clients can keep requests in flight to gain one extra limit in a new window when skipFailedRequests or skipSuccessfulRequests are used with MemoryStore.","user_interaction":"not_required","vuln_class":"security_feature_bypass","vulnerable_functions":["MemoryStore.resetClient"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-682","name":"Incorrect Calculation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in express-rate-limit","id":"CVE-2026-126204","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Loofah: Regular expression denial of service in the SVG local-reference check","id":"CVE-2026-126205"},"nickname":null,"packages":[],"prev":{"headline":"Loofah: Mutation XSS in the HTML5 scrubbers through unescaped attribute values","id":"CVE-2026-126203"},"products":["express-rate-limit"],"published":"2026-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-12","vendors":["express-rate-limit"]},"summary":"Clients can keep requests in flight to gain one extra limit in a new window when skipFailedRequests or skipSuccessfulRequests are used with MemoryStore.","url":"https://insights.sbomify.com/CVE-2026-126204/"}