parse-server
Affected
- introduced
9.0.0-alpha.1, fixed9.5.2-alpha.10(semver)
Fixed versions
9.5.2-alpha.10
Fix
- Fixed version
9.5.2-alpha.10npm install [email protected]
Advisory
Also known as: BIT-parse-2026-30972, CVE-2026-30972
Parse Server has a rate limit bypass via batch request endpoint
Impact
Parse Server's rate limiting middleware is applied at the Express middleware layer, but the batch request endpoint (/batch) processes sub-requests internally by routing them directly through the Promise router, bypassing Express middleware including rate limiting. An attacker can bundle multiple requests targeting a rate-limited endpoint into a single batch request to circumvent the configured rate limit.
Any Parse Server deployment that relies on the built-in rate limiting feature is affected.
Patches
The fix adds a pre-flight check in the batch request handler that counts the number of sub-requests targeting each rate-limited path and rejects the entire batch request if any path's count exceeds its configured requestCount.
Note that this is a server-level rate limit that counts sub-requests within a single batch request. Requests already consumed in the current time window by previous individual or batch requests are not counted against the batch, so the effective limit may be higher when combining individual and batch requests. For comprehensive rate limiting protection, use a reverse proxy or WAF.
Workarounds
Use a reverse proxy or web application firewall (WAF) to enforce rate limiting before requests reach Parse Server.
References
Medium Basis: The source's own band: MODERATE
9.0.0-alpha.1, fixed 9.5.2-alpha.10 (semver)9.5.2-alpha.10
9.5.2-alpha.10npm install [email protected]0, fixed 8.6.23 (semver)8.6.23
8.6.23npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0