CVE-2026-66009: Parse Server 9.0.0 Information Disclosure via GraphQL Error Messages

Published Jul 24, 2026
·
Updated

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

2 affected components
Parse Parse Server>=9.0.0<9.10.0-alpha.5
Parse Parse Server>=8.2.2<8.6.86

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 9.10.0-alpha.5
  2. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 8.6.86

Event History

Jul 24, 2026
CVE Published
via MITRE·12:07 PM
Data Sourced
via MITRE·12:07 PM
DescriptionWeakness
Data Sourced
via NVD·01:18 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-66009?

The severity of CVE-2026-66009 is medium with a score of 6.3.

2

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.

3

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.

4

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.

5

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.

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