All vulnerabilities

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
Weakness
Information exposure through error messages (CWE-209)
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…

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

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.

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.92
  • From 9.0.0 before 9.10.1-alpha.12

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