CVE-2026-116164: Parse Server 9.0.0 before 9.10.4 Reserved Field Name Injection via Object Writes

Published Oct 25, 2026
·
Updated

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

3 affected componentsFixes available
Parse Platform Parse Server<8.6.100, >=9.0.0<9.10.4-alpha.3
bitnami/parse<8.6.100
8.6.100
bitnami/parse>=9.0.0<9.10.4
9.10.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade bitnami/parse to a version that resolves this vulnerability.

    Fixed in 8.6.100
  2. Upgrade

    Upgrade bitnami/parse to a version that resolves this vulnerability.

    Fixed in 9.10.4

Event History

Oct 25, 2026
CVE Published
via MITRE·01:20 PM
Data Sourced
via MITRE·01:20 PM
DescriptionWeakness
Data Sourced
via OSV·01:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness
Oct 30, 2026
Advisory Published
via OSV·03:35 PM
Data Sourced
via OSV·03:35 PM
Affected Software

Frequently Asked Questions

1

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.

2

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.

3

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203