Skip to main content
LowAPIOWASP A05:2021CWE-200

How to fix: GraphQL introspection field suggestions

Field suggestions on error responses let attackers enumerate the schema.

Why it matters

Field suggestions in GraphQL error messages let attackers enumerate valid field names one request at a time, reconstructing the schema even when introspection is disabled, exposing internal data models and admin-only fields.

Field suggestions on error responses let attackers enumerate the schema.

How to fix it

  1. 1Disable field suggestions using Apollo's formatError hook in production
  2. 2In Yoga, configure maskedErrors to replace suggestion text with a generic message
  3. 3Log full errors server-side only; return a generic message to clients

Code examples

Apollo Server 4: disable suggestions

JavaScript
import { ApolloServer } from '@apollo/server';

const server = new ApolloServer({
  typeDefs,
  resolvers,
  formatError(formattedError) {
    if (process.env.NODE_ENV === 'production') {
      return { message: 'Internal server error' };
    }
    return formattedError;
  },
});

GraphQL Yoga: masked errors

JavaScript
import { createYoga, maskError } from 'graphql-yoga';

const yoga = createYoga({
  schema,
  maskedErrors: {
    maskError(error, message) {
      return maskError(error, 'Unexpected error');
    },
  },
});

References

Detected automatically by VulnRadar. The check id is api-graphql-suggestions-enabled, stable across every scan so you can filter or diff on it.

See every api check

Questions

How severe is GraphQL introspection field suggestions?
VulnRadar rates this low severity in the api 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 api-graphql-suggestions-enabled, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does GraphQL introspection field suggestions 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.

Propose a checkHow a check is built

Scan your own site for graphql introspection field suggestions

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

GraphQL introspection field suggestions fix | VulnRadar