Schema metadata disclosure via GraphQL error messages
Published Jul 24, 2026 · Updated Jul 24, 2026
Information disclosure in affected Parse Server releases allows remote attackers to read hidden schema class names through GraphQL errors. The GraphQL error-message sanitizer fails to redact Pointer and Relation target type identifiers from graphql-js validation and input-coercion errors. Exploitation requires a mounted GraphQL API, disabled public introspection, and the public application ID; it exposes class names but not object data or credentials.
Summary
What happened
Information disclosure in affected Parse Server releases allows remote attackers to read hidden schema class names through GraphQL errors. The GraphQL error-message sanitizer fails to redact Pointer and Relation target type identifiers from graphql-js validation and input-coercion errors. Exploitation requires a mounted GraphQL API, disabled public introspection, and the public application ID; it exposes class names but not object data or credentials.
The record
- CVE
- CVE-2026-66008
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- Parse Platform
- Product
- Parse Server
- Classifications
- CWE-209, T1595
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.2.2 <8.6.87
- Affected versionversion=9.0.0 <9.10.0-alpha.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo