dbcve.org
Parse ServerApplication · Parseplatform

CVE-2026-30854

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-07
Fix available
A fix is available. Upgrade to 9.5.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. From version 9.3.1-alpha.3 to before version 9.5.0-alpha.10, when graphQLPublicIntrospection is disabled, __type queries nested inside inline fragments (e.g. ... on Query { __type(name:"User") { name } }) bypass the introspection control, allowing unauthenticated users to perform type reconnaissance. __schema introspection is not affected. This issue has been patched in version 9.5.0-alpha.10.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Parse Server has a GraphQL introspection bypass vulnerability where __type queries nested inside inline fragments (e.g., ... on Query { __type(name:"User") { name } }) bypass the graphQLPublicIntrospection control, allowing unauthenticated users to perform type reconnaissance even when public introspection is disabled.

MitigationUpgrade Parse Server to version 9.5.0-alpha.10 or later to patch the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Parse ServerApplication
Affected:>= 9.4.0, < 9.5.0= 9.3.1= 9.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Parse Server version
    Run `parse-server --version` or check the version field in your project's package.json file
    Affected if The installed version is 9.3.1, or falls within 9.4.0 to 9.5.0 (excluding 9.5.0-alpha.10 and later)
  2. Verify GraphQL API is enabled
    Check your Parse Server configuration (config.json or environment variables) for the graphQL column in the class-level permissions or graphQL schema settings
    Affected if GraphQL is enabled and exposed to unauthenticated users
  3. Confirm graphQLPublicIntrospection is disabled
    Check your Parse Server configuration for the graphQLPublicIntrospection setting - look for it set to false or inspect the GraphQL schema configuration
    Affected if graphQLPublicIntrospection is set to false (the bypass allows introspection even when this control is disabled)
  4. Test for the introspection bypass
    Send a GraphQL query with an inline fragment containing a nested __type request: `query { ... on Query { __type(name: "User") { name } } }` to your /graphql endpoint without authentication
    Affected if The query returns type information (such as the "User" type name) despite public introspection supposedly being disabled

You are affected if your Parse Server version is 9.3.1 or between 9.4.0 and 9.5.0, GraphQL is enabled, and the inline fragment bypass query successfully returns type information even with graphQLPublicIntrospection disabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.5.0 or later
Fixed in 9.5.0
Interim mitigation

Upgrade Parse Server to version 9.5.0-alpha.10 or later to patch the vulnerability.

Recommended fix High confidence

9.5.0-alpha.10 or later (9.5.x stable releases)

  1. 1. Identify the current Parse Server version in use by checking package.json or running the server with version inspection
  2. 2. Upgrade Parse Server to version 9.5.0-alpha.10 or later (such as 9.5.1 stable if available) by running: npm install [email protected] or npm install parse-server@latest
  3. 3. Verify the upgrade completed successfully by checking the installed version
  4. 4. Restart the Parse Server service to apply the new version
  5. 5. Confirm that the graphQLPublicIntrospection setting is properly configured (should be false to enable the introspection protection)
  6. 6. Test that __type queries nested inside inline fragments are now blocked when introspection is disabled
Caveat Alpha versions may contain untested features; if stability is critical, wait for a stable 9.5.x release or verify the patch is included in the stable version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Parse Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30854 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30854 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data