CVE-2026-116164: Parse Server 9.0.0 before 9.10.4 Reserved Field Name Injection via Object Writes
Parse Server before 8.6.100 and 9.0.0 before 9.10.4 does not reject reserved internal field names in client object writes, allowing clients to store or clear internal fields. Attackers can write a reserved field that makes reads of an object fail on MongoDB, disrupting queries on that class for all users, or clear their own account lockout state and password history to bypass lockout and password policies.
Other sources
Parse Server before 8.6.100 and 9.0.0 before 9.10.4-alpha.3 does not reject reserved internal field names in client object writes, allowing clients to store or clear internal fields. Attackers can write a reserved field that makes reads of an object fail on MongoDB, disrupting queries on that class for all users, or clear their own account lockout state and password history to bypass lockout and password policies.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
bitnami/parseto a version that resolves this vulnerability.Fixed in 8.6.100 - Upgrade
Upgrade
bitnami/parseto a version that resolves this vulnerability.Fixed in 9.10.4
Event History
Frequently Asked Questions
Which Parse Server release lines require remediation?
Deployments running versions before 8.6.100 are affected. In the 9.x line, versions from 9.0.0 through before 9.10.4-alpha.3 are affected.
What access would an attacker need to exploit this issue?
The attacker needs the ability to submit client object writes. They can use those writes to set or clear reserved internal fields that should not be client-controlled.
What are the practical security impacts?
An attacker can write a reserved field that causes MongoDB reads of an object to fail, disrupting queries for all users of the affected class. They can also clear their own account lockout state and password history, bypassing lockout and password policies.