Servers and applications
GHSA-gxxq-pghq-9vrc
GraphQL schema is disclosed by replaying an automatic persisted query when public introspection is disabled
- Severity
- Medium 6.3
- Published
- 22 Sept 2026
- Last changed
- 22 Sept 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 8.6.94, 9.10.1-alpha.14
- 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 return the complete GraphQL schema to an unauthenticated caller even when public introspection is disabled, which is the default. The introspection control inspects only the operation text that a client sends directly with a request, so it does not apply when Apollo Server resolves an operation from its automatic persisted query cache. A caller holding only the publicly distributed Application Id and client key can then retrieve the schema, including names of classes and fields that the control is meant to keep private.
Only deployments that mount the GraphQL API are affected. It is not mounted by default. No user data is exposed, and class-level and object-level permissions continue to govern all data access.
Exploitation additionally depends on a client authenticated with the master key or the maintenance key having previously registered an automatic persisted query for the introspection operation on the same server process.
Workarounds
Deployments that do not need the GraphQL API can leave it unmounted, which is the default. Where the API is required, ensure that clients authenticated with the master key or the maintenance key do not use automatic persisted queries against the same server process, because the cache must be populated by such a client before the issue can be triggered. Restarting the process clears the cache. On Parse Server 8, and on Parse Server 9 before 9.3.1, setting NODE_ENV to production additionally activates Apollo Server's own introspection control.
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-gxxq-pghq-9vrc
- github.com https://github.com/parse-community/parse-server/security/advisories/GHSA-gxxq-pghq-9vrc