Categories
CVE-2026-64627

Vulnerability in Parse Server (CVE-2026-64627)

Summary

Vulnerability in Parse Server (CVE-2026-64627). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.10.0-alpha.4 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-64627 has been found in Parse Server.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Parse Server to 9.10.0-alpha.4 or later.
If unsure, ask your IT team or search "Parse Server CVE-2026-64627" on the vendor's site.

CVE-2026-64627 (Parse Server) — CWE-209
Patched: 9.10.0-alpha.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-209) exists in Parse Server.

📍 Affected scope

Check the vendor advisory for the affected versions of Parse Server.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 9.10.0-alpha.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Parse Server を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade Parse Server to 9.10.0-alpha.4

    ステージング環境で 9.10.0-alpha.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami parse
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"8.6.85"},{"introduced":"9.0.0"},{"fixed":"9.10.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details