CVE-2026-66009: Generation of Error Message Containing Sensitive Information in parse-community parse-server
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.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-66009) affects parse-community's parse-server in versions >=9.0.0 <9.10.0-alpha.5 and >=8.2.2 <8.6.86. When public GraphQL introspection is disabled (graphQLPublicIntrospection: false), the server still returns validation error messages that reveal the names of required (non-null) custom input fields on classes referenced by name. This behavior partially defeats the schema-hiding intent of disabling introspection. The exposure is limited to field names; no stored data, credentials, optional fields, unreferenced classes, or Cloud Code function names are disclosed. The vulnerability has a CVSS 4.0 base score of 6.3 (medium severity). No official remediation or patch information is provided in the available data.
Potential Impact
An unauthenticated attacker possessing only the public application ID can trigger GraphQL validation errors to learn the names of required custom input fields. This leaks schema information that is intended to be hidden by disabling public introspection, potentially aiding further reconnaissance or targeted attacks. However, no sensitive data, credentials, or other internal details are exposed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider restricting access to the GraphQL endpoint or implementing additional application-layer controls to limit schema exposure. Monitor vendor communications for updates regarding patches or official mitigations.
CVE-2026-66009: Generation of Error Message Containing Sensitive Information in parse-community parse-server
Description
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.
CVSS v4.0
Score 6.3medium
Affected software
pkg:github/parse-community/parse-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-66009) affects parse-community's parse-server in versions >=9.0.0 <9.10.0-alpha.5 and >=8.2.2 <8.6.86. When public GraphQL introspection is disabled (graphQLPublicIntrospection: false), the server still returns validation error messages that reveal the names of required (non-null) custom input fields on classes referenced by name. This behavior partially defeats the schema-hiding intent of disabling introspection. The exposure is limited to field names; no stored data, credentials, optional fields, unreferenced classes, or Cloud Code function names are disclosed. The vulnerability has a CVSS 4.0 base score of 6.3 (medium severity). No official remediation or patch information is provided in the available data.
Potential Impact
An unauthenticated attacker possessing only the public application ID can trigger GraphQL validation errors to learn the names of required custom input fields. This leaks schema information that is intended to be hidden by disabling public introspection, potentially aiding further reconnaissance or targeted attacks. However, no sensitive data, credentials, or other internal details are exposed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider restricting access to the GraphQL endpoint or implementing additional application-layer controls to limit schema exposure. Monitor vendor communications for updates regarding patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-23T19:22:30.643Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a63602d9c2644c7f8f15040
Added to database: 07/24/2026, 12:53:01 UTC
Last enriched: 07/31/2026, 14:51:31 UTC
Last updated: 09/07/2026, 22:52:14 UTC
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.