CVE-2026-64627

Info Disclosure

Public PoCInfo Disclosure

Published

21 July 2026

Modified

23 July 2026

CVSS Score v4 6.9

Click a component to see what it means

Raw vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

EPSS Score 0.0047 39th percentile

Risk Priority 41 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-64627 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Software (T1592.002); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-11 (Error Handling) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2026-46180

Vulnerability Data

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.

CWE(s): CWE-209

Related Threats

MITRE ATT&CK Enterprise Techniques

T1592.002 Software Reconnaissance

Adversaries may gather information about the victim's host software that can be used during targeting.

attack.mitre.org →

T1082 System Information Discovery Discovery

An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.

attack.mitre.org →

T1592 Gather Victim Host Information Reconnaissance

Adversaries may gather information about the victim's hosts that can be used during targeting.

attack.mitre.org →

T1595 Active Scanning Reconnaissance

Adversaries may execute active reconnaissance scans to gather information that can be used during targeting.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-0655Shared CWE-209

CVE-2023-47636Shared CWE-209

CVE-2023-40757Shared CWE-209

CVE-2024-31844Shared CWE-209

CVE-2023-32755Shared CWE-209

CVE-2025-15526Shared CWE-209

CVE-2025-36003Shared CWE-209

CVE-2025-66549Shared CWE-209

CVE-2025-46575Shared CWE-209

CVE-2023-38713Shared CWE-209

Affected Assets

—

Parse Server

inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V16.5.1

Mitigating Controls (NIST 800-53 r5) AI

SI-11 Error Handling good match

si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match

prevents

Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match

degrades

Logging policy can require suppression of sensitive data in error messages.

A.8.25 Secure development life cycle partial match

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.