parse-community parse-server up to 8.6.22/9.0.0 9.5.2-alpha.9 Batch Request Endpoint improper control of interaction frequency

Summaryinfo

A vulnerability was found in parse-community parse-server up to 8.6.22/9.0.0 9.5.2-alpha.9. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the component Batch Request Endpoint. Performing a manipulation results in improper control of interaction frequency. This vulnerability is cataloged as CVE-2026-30972. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in parse-community parse-server up to 8.6.22/9.0.0 9.5.2-alpha.9. This affects an unknown code block of the component Batch Request Endpoint. The manipulation with an unknown input leads to a improper control of interaction frequency vulnerability. CWE is classifying the issue as CWE-799. The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests. This is going to have an impact on availability. The summary by CVE is:

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior o 9.5.2-alpha.10 and 8.6.23, 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. This vulnerability is fixed in 9.5.2-alpha.10 and 8.6.23.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-30972 since 03/07/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 8.6.23 or 9.0.0 9.5.2-alpha.10 eliminates this vulnerability. The upgrade is hosted for download at github.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• parse-community

Name

• parse-server

Version

• 8.6.0
• 8.6.1
• 8.6.2
• 8.6.3
• 8.6.4
• 8.6.5
• 8.6.6
• 8.6.7
• 8.6.8
• 8.6.9
• 8.6.10
• 8.6.11
• 8.6.12
• 8.6.13
• 8.6.14
• 8.6.15
• 8.6.16
• 8.6.17
• 8.6.18
• 8.6.19
• 8.6.20
• 8.6.21
• 8.6.22
• 9.0.0 9.5.2-alpha.0
• 9.0.0 9.5.2-alpha.1
• 9.0.0 9.5.2-alpha.2
• 9.0.0 9.5.2-alpha.3
• 9.0.0 9.5.2-alpha.4
• 9.0.0 9.5.2-alpha.5
• 9.0.0 9.5.2-alpha.6
• 9.0.0 9.5.2-alpha.7
• 9.0.0 9.5.2-alpha.8
• 9.0.0 9.5.2-alpha.9

Website

• Product: https://github.com/parse-community/parse-server/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion