Parse Server 9.0.0 before 9.10.4-alpha.4 Unauthenticated Class Schema Deletion on MongoDB
Affects Parse Server before 8.6.101 and 9.0.0 before 9.10.4-alpha.4 on MongoDB deployments. Fixed in 8.6.101 and 9.10.4-alpha.4. The vendor gives no separate severity rating.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 9.10.4-alpha.4, 8.6.101
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Parse Server before 8.6.101 and 9.0.0 before 9.10.4-alpha.4 contains a missing authorization vulnerability on MongoDB deployments that lets clients without the master key delete the stored schema of any class. Unauthenticated attackers can send REST API delete requests targeting the internal _SCHEMA collection to remove field definitions, class-level permissions, and protected fields, exposing data to unauthorized reads and modifications.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- parse-community parse-server
From 9.0.0 · fixed in 9.10.4-alpha.4
- parse-community parse-server
fixed in 8.6.101
References 3
GitHub · parse-community/parse-server
vulncheck.com
GitHub · mehmet-emir-eroglu/CVE-2026-116165
Questions about CVE-2026-116165
What does this mean?
On MongoDB deployments, a client without the master key can delete the stored schema of any class. Deleting it removes field definitions, class-level permissions and protected fields, so data those protected may become readable and modifiable by any client.Source: github.com, vulncheck.com
Am I affected, and how do I check?
Parse Server before 8.6.101, and 9.0.0 before 9.10.4-alpha.4, when the deployment uses MongoDB. To check, compare your Parse Server version with these ranges and confirm which database your deployment uses.Source: github.com, vulncheck.com
What should I do about it?
Upgrade to Parse Server 8.6.101 or later on the 8.x line, or to 9.10.4-alpha.4 or later on the 9.x line.Source: github.com, vulncheck.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data