How to fix: GraphQL Introspection Query Reference Found
The page's client-side bundle contains a reference to a GraphQL introspection query string. This is bundled by nearly every GraphQL client library (Apollo, Relay, graphql-request) for fragment matching and codegen, whether or not the server actually has introspection enabled -- this check cannot confirm the server accepts introspection queries, only that the client code mentions them.
Why it matters
No confirmed impact from this signal alone. If the GraphQL server also has introspection genuinely enabled in production, an attacker could discover the entire schema -- verify separately by sending an introspection query directly to the API endpoint.
Client-side GraphQL tooling routinely ships introspection query text as part of normal operation (schema-aware caching, fragment matching, dev tooling support). Treat this as a prompt to verify server-side introspection is disabled in production, not as confirmation that it is enabled.
How to fix it
- 1Verify whether the server actually accepts an introspection query in production (send a __schema query directly to the GraphQL endpoint).
- 2If it does, disable introspection in production and use environment variables to conditionally enable it.
- 3Implement authentication before allowing introspection.
- 4Consider persisted queries.
Code examples
Disable introspection
const server = new ApolloServer({ typeDefs, resolvers, introspection: process.env.NODE_ENV !== 'production' });References
Detected automatically by VulnRadar. The check id is graphql-introspection, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is GraphQL Introspection Query Reference Found?
- VulnRadar rates this low severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id graphql-introspection, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does GraphQL Introspection Query Reference Found map to?
- It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.