Parse Server has a rate limit bypass via batch request endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · 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 · score source

EPSS

• CVE-2026-30972: 0.36% estimated exploitation activity in the next 30 days; percentile 30.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

11 Mar 2026, 00:21 UTC

Last modified by the source

14 Mar 2026, 03:41 UTC

Source last checked

26 Oct 2026, 12:43 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-775h-3xrc-c228

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-775h-3xrc-c228

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30972

Advisory: Parse Server has a rate limit bypass via batch request endpoint
IDs: CVE-2026-30972, GHSA-775h-3xrc-c228
Record: https://patchnext.com/advisories/cve-2026-30972 (revision 3, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: parse-server 9.5.2-alpha.10, 8.6.23. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm parse-server: affected >= 9.0.0-alpha.1, < 9.5.2-alpha.10; < 8.6.23; fixed in 9.5.2-alpha.10, 8.6.23

## Suggested inspection (read-only)
- `npm ls parse-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on parse-server.
- 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-775h-3xrc-c228 (OSV record GHSA-775h-3xrc-c228 lists affected ranges: npm parse-server >=9.0.0-alpha.1 =0 <8.6.23 (fixed))
- Verified: https://github.com/advisories/GHSA-775h-3xrc-c228 (GitHub-reviewed advisory GHSA-775h-3xrc-c228 lists affected ranges: npm parse-server >=9.0.0-alpha.1 =0 <8.6.23)

Commands are suggestions: review each one before running it.