Is CVE-2026-64627 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-64627 being exploited in the wild.

How severe is CVE-2026-64627?

Informational severity, with a CVSS score of 6.9, published 21 July 2026.

Which products and versions are affected?

Parse Community Parse Server >= 9.0.0, < 9.10.0-alpha.4; < 8.6.85.

Is there a fix for CVE-2026-64627?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-64627 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-64627?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-64627: Parse Community Parse Server schema disclosure in GraphQL variable coercion

Q: Is there a fix for CVE-2026-64627?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-64627 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-64627?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-64627 · Severity: info · CVSS 6.9 · Published 2026-07-21

Parse Server, an open-source backend framework, contains a flaw that allows unauthorized individuals to discover the internal structure of an application's database and custom functions. Even when security settings are enabled to hide this information, the system inadvertently reveals valid names through "Did you mean...?" suggestions in error messages. An attacker could use this information to map out a target's infrastructure, identifying hidden data tables and server-side functions to facilitate further attacks.

Quick answers

Is CVE-2026-64627 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-64627 being exploited in the wild.
How severe is CVE-2026-64627?: Informational severity, with a CVSS score of 6.9, published 21 July 2026.
Which products and versions are affected?: Parse Community Parse Server >= 9.0.0, < 9.10.0-alpha.4; < 8.6.85.
Is there a fix for CVE-2026-64627?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-64627 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-64627?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A schema disclosure vulnerability exists in Parse Server's GraphQL API due to improper error handling during variable coercion. While the 'graphQLPublicIntrospection' setting (default: false) is intended to prevent schema discovery, the system still returns 'Did you mean...?' suggestions in error messages when a user provides near-miss enum values or input-object field names. This occurs because the existing introspection-hardening controls only applied to the validation phase, not the variable coercion phase. An unauthenticated remote attacker with only the public application ID can iteratively brute-force and recover hidden schema identifiers, including Cloud Code function names and Parse class/field names. This issue is a bypass of a previous fix (GHSA-8cph-rgr4-g5vj) and is resolved in versions 9.10.0-alpha.4 and 8.6.85.

Affected products

Parse Community Parse Server >= 9.0.0, < 9.10.0-alpha.4; < 8.6.85

Timeline

2026-07-08: advisory: GitHub advisory published by maintainers
2026-07-21: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.