Security Test: Duplicate Query/Mutation Name¶

Scanner(s) Support¶

Description¶

Default Severity: info

This issue occurs when multiple queries or mutations share the same name in your GraphQL schema. Having duplicate operation names can lead to ambiguity in API calls, unexpected behavior, and potential security issues where the wrong operation might be executed. It's important to maintain unique names for all operations to ensure clarity and prevent conflicts.

Reference:

• https://graphql.org/learn/best-practices/#naming-conventions

Configuration¶

Identifier: schema/duplicate_query_or_mutation_name

Examples¶

All configuration available:

checks:
  schema/duplicate_query_or_mutation_name:
    skip: false # default

Compliance and Standards¶