CVE-2026-30939
Parseplatform Parse-Server ≤ 8.6.13
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-30939 is a high-severity Prototype Pollution (CWE-1321) vulnerability in Parseplatform Parse-Server. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-30939 affects Parse Server, an open source backend deployable on any Node.js infrastructure. In versions prior to 8.6.13 and 9.5.1-alpha.2, the vulnerability allows an unauthenticated attacker to crash the Parse Server process by invoking the Cloud Function endpoint with a prototype property name as the function name, triggering infinite recursion and a call stack size error that terminates the process. Additionally, other prototype property names or dot-notation traversal can bypass Cloud Function dispatch validation, resulting in HTTP 200 responses for undefined functions. All deployments exposing the Cloud Function endpoint are vulnerable, with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and mapped to CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').
An unauthenticated remote attacker can exploit this over the network with low complexity and no privileges required. By sending a crafted request to the Cloud Function endpoint using specific prototype property names, the attacker induces a denial-of-service condition via process crash. Alternatively, using other prototype properties or dot-notation, the attacker bypasses validation to elicit misleading HTTP 200 responses, potentially aiding further reconnaissance or chaining attacks, though no direct confidentiality or integrity impact is present.
The Parse community advisories recommend upgrading to Parse Server 8.6.13 or 9.5.1-alpha.2, where the issue is fixed. Details are available in the GitHub security advisory GHSA-5j86-7r7m-p8h6 and release notes for the patched versions at https://github.com/parse-community/parse-server/releases/tag/8.6.13 and https://github.com/parse-community/parse-server/releases/tag/9.5.1-alpha.2.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-10549
Vulnerability Data
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 8.6.13 and 9.5.1-alpha.2, an unauthenticated attacker can crash the Parse Server process by calling a Cloud Function endpoint with a…
more
prototype property name as the function name. The server recurses infinitely, causing a call stack size error that terminates the process. Other prototype property names bypass Cloud Function dispatch validation and return HTTP 200 responses, even though no such Cloud Functions are defined. The same applies to dot-notation traversal. All Parse Server deployments that expose the Cloud Function endpoint are affected. This vulnerability is fixed in 8.6.13 and 9.5.1-alpha.2.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.3.6
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches prototype-pollution flaws before release.
Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.
Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.
Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.
Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.
Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.