CVE-2026-30939
Infinite Recursion Crash in Parse Server Cloud Functions
Publication date: 2026-03-10
Last updated on: 2026-03-11
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| parseplatform | parse-server | to 8.6.13 (exc) |
| parseplatform | parse-server | From 9.0.0 (inc) to 9.5.1 (exc) |
| parseplatform | parse-server | 9.5.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1321 | The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Parse Server, an open source backend for Node.js. Before versions 8.6.13 and 9.5.1-alpha.2, an unauthenticated attacker could crash the Parse Server by calling a Cloud Function endpoint using a prototype property name as the function name. This causes the server to recurse infinitely, leading to a call stack size error that terminates the process.
Additionally, using other prototype property names or dot-notation traversal can bypass Cloud Function dispatch validation, causing the server to return HTTP 200 responses even though no such Cloud Functions exist.
All Parse Server deployments exposing the Cloud Function endpoint are affected by this issue.
How can this vulnerability impact me? :
The vulnerability allows an unauthenticated attacker to crash the Parse Server process, causing a denial of service by terminating the server unexpectedly.
Furthermore, the bypass of Cloud Function dispatch validation may lead to unexpected behavior or confusion, as the server returns successful HTTP 200 responses for undefined functions.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade your Parse Server deployment to version 8.6.13 or later, or 9.5.1-alpha.2 or later, where the issue is fixed.
Ensure that your Cloud Function endpoint is not exposed to unauthenticated users until the upgrade is applied, as the vulnerability allows unauthenticated attackers to crash the server.