graphql-threat-matrix was built for bug bounty hunters, security researchers and hackers to assist with uncovering vulnerabilities across multiple GraphQL implementations.

The differences in how GraphQL implementations interpret and conform to the GraphQL specification may lead to security gaps and unique attack vectors. By analyzing and comparing the factors that drive the security risks across different implementations the GraphQL ecosystem can make safer deployment decisions as well as collectively advance the security maturity of all implementations.

Legend
✅  – Enabled by Default
⚠️  – Disabled by Default
❌  – No Support

ImplementationValidationsField SuggestionsQuery Depth limitQuery Cost AnalysisAutomatic Persisted QueriesIntrospectionDebug ModeBatch Requests
wp-graphql38⚠️⚠️⚠️
graphql-php37⚠️⚠️⚠️⚠️
Apollo34⚠️⚠️
graphql-yoga34⚠️⚠️⚠️⚠️
graphene34⚠️
Ariadne34⚠️⚠️⚠️
Strawberry34⚠️
graphql-ruby28⚠️⚠️
Sangria27⚠️⚠️⚠️
Tartiflette26
graphql-java26⚠️⚠️⚠️
gqlgen25⚠️⚠️⚠️⚠️
Dgraph25⚠️
graphql-go24⚠️
juniper24⚠️
Diana.jl10
gql-dart/gql9
Agoo1⚠️

For Penetration Testers

Use graphw00f to fingerprint a target GraphQL API and determine the backend implementation.