Rate Limiting Bypass in express-brute
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm express-brute
- Affected
- <= 1.0.1
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-984p-xq9m-4rjw lists affected ranges: npm express-brute >=0 <=1.0.1
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-984p-xq9m-4rjw lists affected ranges: npm express-brute >=0 <=1.0.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.6 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
All versions of express-brute are vulnerable to Rate Limiting Bypass. Concurrent requests may lead to race conditions that cause the package to incorrectly count requests. This may allow an attacker to bypass the rate limiting provided by the package and execute requests without limiting. Recommendation No fix is currently available. Consider using an alternative module until a fix is made available.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-984p-xq9m-4rjw
- Revision 1 · created ·
Published from osv record GHSA-984p-xq9m-4rjw
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-984p-xq9m-4rjw Advisory: Rate Limiting Bypass in express-brute IDs: GHSA-984p-xq9m-4rjw Record: https://patchnext.com/advisories/ghsa-984p-xq9m-4rjw (revision 2, source checked 26 Oct 2026, 12:06 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm express-brute: affected <= 1.0.1 ## Suggested inspection (read-only) - `npm ls express-brute --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on express-brute. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-984p-xq9m-4rjw (OSV record GHSA-984p-xq9m-4rjw lists affected ranges: npm express-brute >=0 <=1.0.1) - Verified: https://github.com/advisories/GHSA-984p-xq9m-4rjw (GitHub-reviewed advisory GHSA-984p-xq9m-4rjw lists affected ranges: npm express-brute >=0 <=1.0.1) Commands are suggestions: review each one before running it.
Loading voting…