CVE-2026-30972: Parse server Parse Server Has A Rate Vulnerability

MODERATE
Advisory Identifier: GHSA-775h-3xrc-c228
Share
CWE-799
Published
Advisory Summary

CVE-2026-30972 is a MODERATE parse server has a rate vulnerability (CWE-799: Improper Control of Interaction Frequency) affecting Parse server libraries in the npm ecosystem. The issue involves parse server has a rate limit bypass via batch request endpoint. Remediation is available by upgrading affected packages to version 9.5.2-alpha.10, 8.6.23.

CVE-2026-30972 at a Glance

CVE Identifier CVE-2026-30972
GHSA Identifier GHSA-775h-3xrc-c228
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-799: Improper Control of Interaction Frequency
Affected Product Parse server
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-30972

To remediate this vulnerability, upgrade all affected Parse server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

parse-server fixed: 9.5.2-alpha.10 
npm install parse-server@9.5.2-alpha.10
parse-server fixed: 8.6.23 
npm install parse-server@8.6.23
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls parse-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-30972, inspect your project dependencies using npm:

npm ls parse-server

Analyze the terminal output to locate any version of Parse server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.5.2-alpha.10), your application is affected.

Note: The npm ls parse-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-799: Improper Control of Interaction Frequency, where 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. In Parse server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-775h-3xrc-c228 - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.10 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.23

CVE-2026-30972 Affected Parse server Versions

2 component(s)
Fixed Versions:
9.5.2-alpha.108.6.23
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm/parse-server
npm
≥ 9.0.0-alpha.1
< 9.5.2-alpha.10
9.5.2-alpha.10
parse-server
npm/parse-server
npm
< 8.6.23
8.6.23

References

GitHub Advisory / Wiki ADVISORY
https://github.com/parse-community/parse-server/security/advisories/GHSA-775h-3xrc-c228
NVD — CVE-2026-30972 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-30972
Parse server Source Repository REPOSITORY
https://github.com/parse-community/parse-server
Parse server Release RELEASE
https://github.com/parse-community/parse-server/releases/tag/8.6.23
Parse server Release RELEASE
https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.10

Frequently Asked Questions

What is CVE-2026-30972?
CVE-2026-30972 is a security vulnerability in Parse server involving Parse Server has a rate limit bypass via batch request endpoint under CWE-799: Improper Control of Interaction Frequency.
Which Parse server versions are affected?
Affected versions include releases prior to 9.5.2-alpha.10, 8.6.23 across affected packages: parse-server.
What version fixes CVE-2026-30972?
Upgrading to 9.5.2-alpha.10, 8.6.23 (or the latest patched release for your respective branch) resolves the vulnerability.
Is parse-server affected?
Yes, parse-server is affected in releases prior to 9.5.2-alpha.10, 8.6.23. Upgrade your dependency to 9.5.2-alpha.10, 8.6.23 or later.
What CWE is associated with CVE-2026-30972?
CVE-2026-30972 is classified under CWE-799: Improper Control of Interaction Frequency (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.).
How can I check npm dependencies for CVE-2026-30972?
Run the dependency tree command: 'npm ls parse-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-775h-3xrc-c228",
  "modified" : "2026-03-11T00:21:51Z",
  "published" : "2026-03-11T00:21:51Z",
  "aliases" : [ "CVE-2026-30972" ],
  "summary" : "Parse Server has a rate limit bypass via batch request endpoint",
  "details" : "### Impact\n\nParse 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.\n\nAny Parse Server deployment that relies on the built-in rate limiting feature is affected.\n\n### Patches\n\nThe 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`.\n\nNote 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.\n\n### Workarounds\n\nUse a reverse proxy or web application firewall (WAF) to enforce rate limiting before requests reach Parse Server.\n\n### References\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-775h-3xrc-c228\n- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.10\n- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.23",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0-alpha.1"
      }, {
        "fixed" : "9.5.2-alpha.10"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.23"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-775h-3xrc-c228"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-30972"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/releases/tag/8.6.23"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.10"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-799" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-11T00:21:51Z",
    "nvd_published_at" : "2026-03-10T21:16:49Z"
  }
}