All vulnerabilities

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
Weakness
Incorrect authorization (CWE-863)
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.

From parse-community/parse-server's security advisory. Shortened; the full text is there.

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.

Workarounds as given by parse-community/parse-server's security advisory.

Affected software

SoftwareAffected versions
Parse ServerServers and applications · github:parse-community/parse-server
  • From 8.2.2 before 8.6.94
  • From 9.0.0 before 9.10.1-alpha.14

About Parse Server

Parse Server for Node.js / Express

From its GitHub repository.
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

References