CVE-2026-116164

Parse Server 9.0.0 before 9.10.4-alpha.3 Reserved Field Name Injection via Object Writes

Published Oct 25, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Parse Server before 8.6.100 and 9.0.0 before 9.10.4-alpha.3 allows clients to write reserved internal field names, enabling storage or clearing of fields that the system considers internal. This flaw can make object reads fail in MongoDB, disrupting queries for all users, or permit a user to clear their account lockout state and password history, effectively bypassing lockout and password policies. The vulnerability is a classic example of improper input validation.

Affected Systems

The affected systems are Parse Server from parse-community, all versions prior to 8.6.100 and from 9.0.0 up to but not including 9.10.4-alpha.3. Users running these releases should review version and apply the fix.

Risk and Exploitability

The CVSS score of 6.3 indicates moderate severity. No EPSS score is available, and the vulnerability is not listed in CISA’s KEV catalog, suggesting no confirmed exploitation at present. Attackers can exploit the flaw remotely through the application’s client API; authenticated clients can inject reserved field names, so the risk is higher for systems that expose writable endpoints without proper validation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Parse Server to version 9.10.4-alpha.3 or newer, or to 8.6.100 or later.
  • Implement server‑side validation that rejects any writes containing reserved internal field names if an upgrade is not immediately possible.
  • Review and restrict exposed write operations in the Parse Server application to prevent unauthorized clients from modifying internal fields.

Generated by OpenCVE AI on October 25, 2026 at 16:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Parse Community
Parse Community parse Server
Vendors & Products Parse Community
Parse Community parse Server
Type Values Removed Values Added
Description 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.
Title Parse Server 9.0.0 before 9.10.4-alpha.3 Reserved Field Name Injection via Object Writes
First Time appeared Parseplatform
Parseplatform parse-server
Weaknesses CWE-20
CPEs cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:*:*:*
Vendors & Products Parseplatform
Parseplatform parse-server
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-20

    Improper Input Validation

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 4, 2026, 5:26 PM
Reserved
Oct 25, 2026, 12:24 PM
Status
Awaiting Analysis
Published
Oct 25, 2026, 2:16 PM
Modified
Nov 4, 2026, 6:17 PM