CVE-2026-30854: Parse Server: GraphQL `__type` introspection bypass via inline fragments when public introspection is disabled

Published Mar 7, 2026
·
Updated

Impact

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.

Patches

The check was changed from a flat iteration over root-level selections to a recursive walk of all selection sets, detecting type inside inline fragments at any depth.

Workarounds

Require master key authentication at the network layer (e.g. reverse proxy) for the GraphQL endpoint.

References

- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-q5q9-2rhp-33qw - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.10

Other sources

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.

MITRE

Affected Software

14 affected componentsFixes available
npm/parse-server>=9.3.1-alpha.3<9.5.0-alpha.10
npm/parse-server>=9.3.1-alpha.3<9.5.0-alpha.10
9.5.0-alpha.10
parseplatform Parse-server Node.js>=9.4.0<9.5.0
parseplatform Parse-server Node.js=9.3.1-alpha3
parseplatform Parse-server Node.js=9.3.1-alpha4
parseplatform Parse-server Node.js=9.5.0-alpha1
parseplatform Parse-server Node.js=9.5.0-alpha2
parseplatform Parse-server Node.js=9.5.0-alpha3
parseplatform Parse-server Node.js=9.5.0-alpha4
parseplatform Parse-server Node.js=9.5.0-alpha5
parseplatform Parse-server Node.js=9.5.0-alpha6
parseplatform Parse-server Node.js=9.5.0-alpha7
parseplatform Parse-server Node.js=9.5.0-alpha8
parseplatform Parse-server Node.js=9.5.0-alpha9

Event History

Mar 7, 2026
CVE Published
via MITRE·04:24 PM
Data Sourced
via MITRE·04:24 PM
DescriptionWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software
Mar 9, 2026
Advisory Published
via GitHub·05:42 PM
Data Sourced
via GitHub·05:42 PM
DescriptionWeaknessAffected Software
Feb 18, 58167
Event
via FIRST·01:19 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-30854?

CVE-2026-30854 is considered a moderate severity vulnerability due to its potential for bypassing GraphQL introspection.

2

How do I fix CVE-2026-30854?

To fix CVE-2026-30854, you should upgrade Parse Server to version 9.5.0-alpha.10 or later.

3

What is the impact of CVE-2026-30854?

The impact of CVE-2026-30854 allows unauthorized users to access GraphQL schema details when public introspection is disabled.

4

Which versions of Parse Server are affected by CVE-2026-30854?

Parse Server versions from 9.3.1-alpha.3 up to, but not including, 9.5.0-alpha.10 are affected by CVE-2026-30854.

5

Is CVE-2026-30854 related to GraphQL functionality?

Yes, CVE-2026-30854 specifically involves a GraphQL introspection bypass issue in Parse Server.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203