CVE-2026-66009: Parse Server 9.0.0 Information Disclosure via GraphQL Error Messages
Parse Server versions >= 9.0.0 before 9.10.0-alpha.5 and >= 8.2.2 before 8.6.86 return GraphQL validation error messages that name required custom input fields even when public introspection is disabled (graphQLPublicIntrospection: false, the default). A client holding only the public application id — with no user session, master key, or maintenance key — can trigger validation errors to learn the names of required (non-null) custom fields on classes it already references by name, partially defeating the schema-hiding intent of disabling public introspection. No stored data, credentials, optional field names, unreferenced class names, or Cloud Code function names are exposed.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Parse Serverto a version that resolves this vulnerability.Fixed in 9.10.0-alpha.5 - Upgrade
Upgrade
Parse Serverto a version that resolves this vulnerability.Fixed in 8.6.86
Event History
Frequently Asked Questions
What is the severity of CVE-2026-66009?
The severity of CVE-2026-66009 is medium with a score of 6.3.
How do I fix CVE-2026-66009?
To fix CVE-2026-66009, upgrade Parse Server to version 9.10.0-alpha.5 or later, or to version 8.6.86 or later.
What systems are affected by CVE-2026-66009?
CVE-2026-66009 affects Parse Server versions 9.0.0 through 9.10.0-alpha.5 and 8.2.2 through 8.6.86.
What is the exploit method for CVE-2026-66009?
CVE-2026-66009 can be exploited by sending GraphQL requests that trigger validation errors revealing sensitive information.
What data is potentially exposed by CVE-2026-66009?
CVE-2026-66009 can lead to the disclosure of required custom input field names in error messages, even with public introspection disabled.