How to fix: GraphQL error response leaks stack trace
Stack traces in error.extensions.stacktrace expose file paths, framework versions, and SQL fragments to any unauthenticated caller.
Why it matters
Stack traces embedded in API responses reveal internal file system paths, framework versions, database schema details, and SQL fragments, giving attackers the reconnaissance needed to craft targeted injection or path traversal attacks.
Stack traces in error.extensions.stacktrace expose file paths, framework versions, and SQL fragments to any unauthenticated caller.
How to fix it
- 1Use Apollo's formatError hook to strip stack traces in production
- 2Log full errors server-side and return only a generic message to clients
- 3Gate stack traces on NODE_ENV: development only
Code examples
Apollo Server: strip stack traces in production
const server = new ApolloServer({
typeDefs,
resolvers,
formatError(formattedError, error) {
console.error(error);
if (process.env.NODE_ENV === 'production') {
return {
message: formattedError.message,
extensions: { code: formattedError.extensions?.code },
};
}
return formattedError;
},
});References
Detected automatically by VulnRadar. The check id is api-graphql-error-stack-trace, stable across every scan so you can filter or diff on it.
More api checks
- LowTRACE method referenced in API response body
- InfoREST endpoint allows DELETE
- LowGraphQL introspection field suggestions
- MediumGraphQL endpoint has no rate-limit headers
- LowOpenAPI server URL leaks internal host
- LowCORS preflight result not cached
- HighBearer token in URL query string
- MediumJSONP callback parameter accepted
Questions
- How severe is GraphQL error response leaks stack trace?
- VulnRadar rates this medium 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-error-stack-trace, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does GraphQL error response leaks stack trace map to?
- It maps to CWE-209. 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.