# CVE-2026-64627: Parse Server 9.0.0 Schema Disclosure via GraphQL Variable Coercion

> Unauthenticated attackers can recover hidden schema details like class and field names via GraphQL error messages, bypassing introspection restrictions.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** BIT-parse-2026-64627, GHSA-9g8f-h8f3-hjcm, GHSA-rjjh-vx7v-m7mf

## What is CVE-2026-64627?

CVE-2026-64627 is a medium-severity vulnerability in parse-community parse-server, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Parse Server versions >= 9.0.0 before 9.10.0-alpha.4 and versions before 8.6.85 contain a schema disclosure vulnerability. When the GraphQL API is mounted with public introspection disabled (graphQLPublicIntrospection: false, the default), schema-derived 'Did you mean ...?' suggestions were still returned in GraphQL error messages produced during variable coercion, which were not covered by the introspection-hardening control (that only handled validation errors). An unauthenticated caller possessing only the public application id can iteratively recover hidden schema identifiers — including registered Cloud Code function names and Parse class and field names — by submitting queries or mutations whose variables contain near-miss enum values or input-object field names. This is a follow-up bypass of GHSA-8cph-rgr4-g5vj. The issue is fixed in 9.10.0-alpha.4 and 8.6.85.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2026-64627?

1 open source package ship an affected version, including parse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `parse` | Bitnami | All versions | 8.6.85, 9.10.0 |

## How do I fix CVE-2026-64627?

Upgrade parse to a fixed version for your release line: 8.6.85 or 9.10.0.

## Is CVE-2026-64627 being exploited?

There is no known exploitation of CVE-2026-64627 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64627 and fix it if it is affected.

What it is: CVE-2026-64627 is a medium-severity vulnerability in parse-community parse-server, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64627 in the wild and no public exploit code.

Affected packages and fixed versions:
- parse (Bitnami): affected all versions; fixed in 8.6.85, 9.10.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64627/ (Markdown: https://insights.sbomify.com/CVE-2026-64627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64627
- OSV: https://osv.dev/vulnerability/CVE-2026-64627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64627/
Summaries are generated and may contain mistakes; the official description above is the record.