CVE-2026-66009: Parse Server 9.0.0 Information Disclosure via GraphQL Error Messages
parse-community · parse-server
Vendor fix available · Affected: parse-community parse-server · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 39% of scored CVEs
DescriptionCVE.org
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 products2
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- parse-community · parse-serverfrom 9.0.0 before 9.10.0-alpha.5
- parse-community · parse-serverfrom 8.2.2 before 8.6.86
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- parse-community
- Published
- July 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-66009 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.