Parse Server 9.0.0 before 9.10.4 Unauthenticated Class Schema Deletion on MongoDB

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/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:X · score source

EPSS

• CVE-2026-116165: 0.32% estimated exploitation activity in the next 30 days; percentile 24.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Parse Server before 8.6.101 and 9.0.0 before 9.10.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.

Published by the source

30 Oct 2026, 15:35 UTC

Last modified by the source

30 Oct 2026, 20:56 UTC

Source last checked

31 Oct 2026, 07:05 UTC

1. Revision 1 · created · 31 Oct 2026

   Published from osv record BIT-parse-2026-116165

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-116165

Advisory: Parse Server 9.0.0 before 9.10.4 Unauthenticated Class Schema Deletion on MongoDB
IDs: CVE-2026-116165, GHSA-qmg9-m772-5rm7
Record: https://patchnext.com/advisories/cve-2026-116165 (revision 1, source checked 31 Oct 2026, 07:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: parse 9.10.4, 8.6.101. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami parse: affected < 8.6.101; >= 9.0.0, < 9.10.4; fixed in 9.10.4, 8.6.101

## Suggested inspection (read-only)
- Bitnami parse: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on parse.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/BIT-parse-2026-116165 (OSV record BIT-parse-2026-116165 lists affected ranges: Bitnami parse >=0 =9.0.0 <9.10.4 (fixed))

Commands are suggestions: review each one before running it.