CVE-2026-47248: Parse server Parse Server's GraphQL "Did You Vulnerability

MODERATE
Advisory Identifier: GHSA-8cph-rgr4-g5vj
Share
CWE-209
Published
Advisory Summary

CVE-2026-47248 is a MODERATE parse server's graphql "did you vulnerability (CWE-209: Generation of Error Message Containing Sensitive Information) affecting Parse server libraries in the npm ecosystem. The issue involves parse server's graphql "did you mean ...?" validation suggestions disclose schema to unauthenticated callers. Remediation is available by upgrading affected packages to version 9.9.1-alpha.2, 8.6.78.

CVE-2026-47248 at a Glance

CVE Identifier CVE-2026-47248
GHSA Identifier GHSA-8cph-rgr4-g5vj
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-209: Generation of Error Message Containing Sensitive Information
Affected Product Parse server
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-47248

To remediate this vulnerability, upgrade all affected Parse server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

parse-server fixed: 9.9.1-alpha.2 
npm install parse-server@9.9.1-alpha.2
parse-server fixed: 8.6.78 
npm install parse-server@8.6.78
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls parse-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-47248, inspect your project dependencies using npm:

npm ls parse-server

Analyze the terminal output to locate any version of Parse server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.9.1-alpha.2), your application is affected.

Note: The npm ls parse-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-209: Generation of Error Message Containing Sensitive Information, where the product generates an error message that includes sensitive information about its environment, users, or associated data. In Parse server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Parse Server's GraphQL endpoint discloses schema metadata to unauthenticated callers through `Did you mean ...?` suggestions embedded in GraphQL validation-error messages. An unauthenticated caller who knows only the public application id can iteratively send malformed queries to reconstruct class names, field names, argument names, mutation names, and input-object fields. This bypasses the `IntrospectionControlPlugin` enforced when `graphQLPublicIntrospection: false` (the default) and defeats the schema-hiding goal of prior advisories GHSA-48q3-prgv-gm4w and GHSA-q5q9-2rhp-33qw. Schema disclosure aids reconnaissance for downstream authorization probing but does not by itself leak object data or authentication material. ### Patches A new `SchemaSuggestionsControlPlugin` Apollo plugin strips the `Did you mean ...?` suffix from GraphQL validation-error messages during `validationDidStart`, which runs before any introspection gate. The plugin applies only when `graphQLPublicIntrospection: false` and the caller is not a master-key or maintenance-key holder, matching the trust model of the existing `IntrospectionControlPlugin`. ### Workarounds No code workaround is available short of disabling the GraphQL API (`mountGraphQL: false`). Operators who require disclosure-resistant validation errors should upgrade to a patched release. ### Resources - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-8cph-rgr4-g5vj - Fix Parse Server 9: https://github.com/parse-community/parse-server/pull/10467 - Fix Parse Server 8: https://github.com/parse-community/parse-server/pull/10468

CVE-2026-47248 Affected Parse server Versions

2 component(s)
Fixed Versions:
9.9.1-alpha.28.6.78
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm/parse-server
npm
≥ 9.0.0
< 9.9.1-alpha.2
9.9.1-alpha.2
parse-server
npm/parse-server
npm
< 8.6.78
8.6.78

References

GitHub Advisory / Wiki ADVISORY
https://github.com/parse-community/parse-server/security/advisories/GHSA-8cph-rgr4-g5vj
NVD — CVE-2026-47248 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-47248
Parse server Source Repository REPOSITORY
https://github.com/parse-community/parse-server/pull/10467
Parse server Source Repository REPOSITORY
https://github.com/parse-community/parse-server/pull/10468
Parse server Source Repository REPOSITORY
https://github.com/parse-community/parse-server

Frequently Asked Questions

What is CVE-2026-47248?
CVE-2026-47248 is a security vulnerability in Parse server involving Parse Server's GraphQL "Did you mean ...?" validation suggestions disclose schema to unauthenticated callers under CWE-209: Generation of Error Message Containing Sensitive Information.
Which Parse server versions are affected?
Affected versions include releases prior to 9.9.1-alpha.2, 8.6.78 across affected packages: parse-server.
What version fixes CVE-2026-47248?
Upgrading to 9.9.1-alpha.2, 8.6.78 (or the latest patched release for your respective branch) resolves the vulnerability.
Is parse-server affected?
Yes, parse-server is affected in releases prior to 9.9.1-alpha.2, 8.6.78. Upgrade your dependency to 9.9.1-alpha.2, 8.6.78 or later.
What CWE is associated with CVE-2026-47248?
CVE-2026-47248 is classified under CWE-209: Generation of Error Message Containing Sensitive Information (The product generates an error message that includes sensitive information about its environment, users, or associated data.).
How can I check npm dependencies for CVE-2026-47248?
Run the dependency tree command: 'npm ls parse-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8cph-rgr4-g5vj",
  "modified" : "2026-06-12T21:59:48Z",
  "published" : "2026-05-29T19:18:01Z",
  "aliases" : [ "CVE-2026-47248" ],
  "summary" : "Parse Server's GraphQL \"Did you mean ...?\" validation suggestions disclose schema to unauthenticated callers",
  "details" : "### Impact\n\nParse Server's GraphQL endpoint discloses schema metadata to unauthenticated callers through `Did you mean ...?` suggestions embedded in GraphQL validation-error messages. An unauthenticated caller who knows only the public application id can iteratively send malformed queries to reconstruct class names, field names, argument names, mutation names, and input-object fields. This bypasses the `IntrospectionControlPlugin` enforced when `graphQLPublicIntrospection: false` (the default) and defeats the schema-hiding goal of prior advisories GHSA-48q3-prgv-gm4w and GHSA-q5q9-2rhp-33qw. Schema disclosure aids reconnaissance for downstream authorization probing but does not by itself leak object data or authentication material.\n\n### Patches\n\nA new `SchemaSuggestionsControlPlugin` Apollo plugin strips the `Did you mean ...?` suffix from GraphQL validation-error messages during `validationDidStart`, which runs before any introspection gate. The plugin applies only when `graphQLPublicIntrospection: false` and the caller is not a master-key or maintenance-key holder, matching the trust model of the existing `IntrospectionControlPlugin`.\n\n### Workarounds\n\nNo code workaround is available short of disabling the GraphQL API (`mountGraphQL: false`). Operators who require disclosure-resistant validation errors should upgrade to a patched release.\n\n### Resources\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-8cph-rgr4-g5vj\n- Fix Parse Server 9: https://github.com/parse-community/parse-server/pull/10467\n- Fix Parse Server 8: https://github.com/parse-community/parse-server/pull/10468",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0"
      }, {
        "fixed" : "9.9.1-alpha.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.78"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-8cph-rgr4-g5vj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-47248"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10467"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10468"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-209" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-29T19:18:01Z",
    "nvd_published_at" : "2026-06-12T19:16:28Z"
  }
}