# CVE-2026-30939: parse-server — Fixed in 8.6.13

📦 npm

Not in CISA KEV

# CVE-2026-30939 — parse-server

CVE-2026-30939 is a CWE-1321 vulnerability in parse-server. A fix is available for parse-server — see the affected versions and patch details below.

Parse Server has Denial of Service (DoS) and Cloud Function Dispatch Bypass via Prototype Chain Resolution

Also known asBIT-parse-2026-30939[GHSA-5j86-7r7m-p8h6](/vulnerability/GHSA-5j86-7r7m-p8h6)

Published

Mar 10, 2026

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-30939.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.6%probability of exploitation in next 30 days

Lower Risk+0.06%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

0.00%0.39%0.78%1.18%0.2%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

62other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`parse-server`npm

54Kdownloads / week

## Description

#### Impact

An unauthenticated attacker can crash the Parse Server process by calling a Cloud Function endpoint with a 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.

#### Patches

The internal handler registries for Cloud Functions, Jobs, Triggers, and Validators have been changed to prevent prototype chain properties from being resolved.

#### Workarounds

Place a reverse proxy or WAF in front of Parse Server and block requests to `Object.prototype` property names.

#### References

-   GitHub security advisory: [https://github.com/parse-community/parse-server/security/advisories/GHSA-5j86-7r7m-p8h6](https://github.com/parse-community/parse-server/security/advisories/GHSA-5j86-7r7m-p8h6)
-   Fix Parse Server 9: [https://github.com/parse-community/parse-server/releases/tag/9.5.1-alpha.2](https://github.com/parse-community/parse-server/releases/tag/9.5.1-alpha.2)
-   Fix Parse Server 8: [https://github.com/parse-community/parse-server/releases/tag/8.6.13](https://github.com/parse-community/parse-server/releases/tag/8.6.13)

## Affected Packages

2 total 2 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`parse-server` 

all versions

8.6.13`npm install parse-server@8.6.13`

📦npm

`parse-server` 

≥ 9.0.0-alpha.1&&< 9.5.1-alpha.2

9.5.1-alpha.2`npm install parse-server@9.5.1-alpha.2`

## Affected Products

1 product · 3 configurations

Application

`parse-server`parseplatform

≥ 9.0.0 && < 9.5.1

1 version

9.5.1

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parse-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update parse-server to 8.6.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-30939 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
    

## Frequently Asked Questions

\### Impact An unauthenticated attacker can crash the Parse Server process by calling a Cloud Function endpoint with a 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. ### Patches The internal handler registries for Cloud Func

O3 Security · Impact-Aware SCA

### Is CVE-2026-30939 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)