Information disclosure in Parse-Community Parse-Server
CVE-2026-66009
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.
Published · last modified .
EPSS exploit prediction
EPSS: 0.004 (37.7th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 38th percentile — 37.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000
Affected products
- Parse-Community Parse-Server — versions 9.0.0, 9.10.0-alpha.5, 8.2.2
Weakness classification (CWE)
References
- github.com/parse-community/parse-server/security/advisories/GHSA-2fgh-8j2g-w354 (vendor-advisory)
- www.vulncheck.com/advisories/parse-server-information-disclosure-via-graphql-er… (third-party-advisory)