Servers and applications
GHSA-6m77-f8xr-f723
GraphQL argument and enum validation errors disclose target class names when public introspection is disabled
- Severity
- Medium 6.3
- Published
- 21 Sept 2026
- Last changed
- 21 Sept 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 8.6.92, 9.10.1-alpha.12
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Read some data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
Parse Server can hide its GraphQL schema from callers that are not permitted to introspect it. When that protection is active, several error messages returned by the GraphQL API still contained the names of generated types that embed application class names. An unauthenticated caller holding only the public Application Id could send a single crafted operation and read back the name of a class that is otherwise hidden — in particular the target class of a pointer or relation field, which the field's own name does not reveal.
Only schema identifiers are affected. No object data, credentials, session tokens or configuration values are exposed, nothing is modified, and availability is unaffected. Access controls on the classes themselves continue to apply.
Deployments that mount the GraphQL API are affected. This is the fifth issue of this kind; the fixes for GHSA-8cph-rgr4-g5vj, GHSA-9g8f-h8f3-hjcm, GHSA-2fgh-8j2g-w354 and GHSA-r2g6-4f6j-f6rf covered other error templates and did not…
Workarounds
No configuration change mitigates this while the GraphQL API is mounted and reachable. Deployments that do not require the GraphQL API can avoid exposure by not mounting it. Where it is required, restricting network access to the GraphQL endpoint to trusted clients limits who can reach the affected error paths. Upgrading is the recommended remediation.
Affected software
| Software | Affected versions |
|---|---|
Parse ServerServers and applications · github:parse-community/parse-server |
|
About Parse Server
Parse Server for Node.js / Express
- Weekly downloads (npm)
- 54,531npm, 15 Nov 2026
- Docker Hub pulls
- 4,250,088Docker Hub, 15 Nov 2026
- GitHub stars
- 21,396GitHub, 15 Nov 2026
- Forks
- 4,811GitHub, 15 Nov 2026
- Latest release
- 8.6.123GitHub, 15 Nov 2026
- Released
- 9 Nov 2026GitHub
- License
- Apache-2.0GitHub
- First published on GitHub
- 28 Jan 2016GitHub
Source code Website Docker image Package
Vulnerabilities in Parse Server
- In our list
- 184
- Published in the last 12 months
- 156
- Critical, last 12 months
- 14
- High, last 12 months
- 52
- Known exploited
- 0
- GHSA-9v83-v857-2xf8Query and LiveQuery subscription constraints disclose the auth data and session token of a userHigh 8.2 19 Nov 2026
- CVE-2026-130671Parse Server before 8.6.119 and 9.x before 9.10.8-alpha.3 LiveQuery Missing AuthorizationMedium 6.3 18 Nov 2026
- GHSA-f92h-3w9f-hg55LiveQuery discloses MFA secrets and auth data that an auth adapter hides to a subscription of the user itselfMedium 5.9 17 Nov 2026
- GHSA-43rg-r2xr-q686Login with auth data discloses MFA secrets and user fields that the user is not allowed to readMedium 5.9 14 Nov 2026
- CVE-2026-126392Parse Server 9.10.6-alpha.1 before 9.10.8-alpha.1 Information Disclosure via Dot Notation UpdateLow 2.3 13 Nov 2026
- GHSA-f6wh-8wcf-xfv8LiveQuery subscription with a large list constraint can block the event loopHigh 8.2 11 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-6m77-f8xr-f723
- github.com https://github.com/parse-community/parse-server/security/advisories/GHSA-6m77-f8xr-f723