VulnerabilityPublished 10 Mar 2026

CVE-2026-30972: parse-server · Improper Control of Interaction Frequency

Affects parse-serverSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 9.5.2-alpha.10 or 8.6.23 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.5.2-alpha.10, 8.6.23

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:L

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Subsequent System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Subsequent System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade parse-server to 9.5.2-alpha.10 or 8.6.23; parse-community/parse-server to 8.6.23.

Affected software

Product	Affected	Fixed in
parse-communityparse-server	Affected >=9.0.0 <9.5.2-alpha.10	Fixed in 9.5.2-alpha.10
parse-communityparse-server	Affected <8.6.23	Fixed in 8.6.23
npmparse-community/parse-server`pkg:npm/parse-community/parse-server`Other threats	Affected <8.6.23	Fixed in 8.6.23

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The most effective mitigation is to upgrade parse-server to version 9.5.2-alpha.10 or later, or 8.6.23 or later, where the batch request endpoint properly enforces rate limiting on sub-requests. Until upgrades can be applied, organizations should consider implementing external rate limiting or API gateway controls that inspect and limit batch requests as a whole and their sub-requests. Monitoring and alerting on unusual batch request volumes or patterns can help detect exploitation attempts. Additionally, restricting access to the batch endpoint to trusted clients or requiring authentication can reduce exposure. Reviewing and tightening resource quotas and backend service limits can mitigate the impact of potential abuse. Network-level protections such as WAF rules to detect and throttle suspicious batch request payloads may also be beneficial. Finally, educating developers and administrators about this vulnerability and ensuring timely patch management is critical.

Description

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.

Impact

The primary impact of this vulnerability is the ability for attackers to bypass rate limiting controls, which can lead to resource exhaustion on the parse-server backend. This can degrade service availability, cause denial of service conditions, and potentially enable further attacks that rely on overwhelming the backend infrastructure. Organizations relying on parse-server's built-in rate limiting for abuse prevention or API usage control are at risk of having these protections nullified. This can affect cloud services, mobile backends, and web applications using parse-server, potentially leading to service disruptions and increased operational costs due to resource overuse. Since no authentication is required, the attack surface is broad, and attackers can exploit this vulnerability remotely. Although no known exploits are reported in the wild yet, the straightforward bypass mechanism makes it a significant risk if unpatched. The vulnerability does not directly expose sensitive data but undermines service integrity and availability.

CWE-799Improper Control of Interaction Frequency (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
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.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 21:15 UTC

WeaknessesCWE-799

Technical details

References

Community reviews

Related threats