Skip to main content

Technology: graphql

IDTitleDescriptionCategoryTechnologyTags
prequel-2025-0006
Low
Impact: 3/10
Mitigation: 7/10
Apollo GraphQL ErrorAn application using Apollo GraphQL is experiencing an error.GraphQL ProblemsgraphqlApolloGraphQLError
prequel-2025-0007
Low
Impact: 3/10
Mitigation: 7/10
GraphQL \"Cannot read properties of undefined\" errorIndicates an error in a subgraph service query during query execution in a federated service.GraphQL ProblemsgraphqlApolloGraphQLError
prequel-2025-0008
Low
Impact: 3/10
Mitigation: 7/10
Apollo GraphQL DOWNSTREAM_SERVICE_ERRORIndicates an error in a subgraph service query during query execution in a federated service.GraphQL ProblemsgraphqlApolloGraphQLError
prequel-2025-0011
Medium
Impact: 7/10
Mitigation: 5/10
GraphQL internal server error due to record not foundThe application is experiencing internal server errors when GraphQL operations attempt to access records that do not exist in the database. This occurs when GraphQL queries reference entities that have been deleted, were never created, or are inaccessible due to permission issues. Instead of handling these cases gracefully with proper error responses, the API is escalating them to internal server errors that may impact client applications and user experience.GraphQL ProblemsgraphqlGraphQLDatabaseErrors
prequel-2025-0012
Medium
Impact: 6/10
Mitigation: 5/10
GraphQL internal server error due to unhandled exception in NestJS resolverThe application is generating internal server errors during GraphQL operations due to uncaught exceptions in resolver logic. These errors are not properly handled or transformed into structured GraphQL responses, resulting in unexpected 500-level failures for client applications. Stack traces often reference NestJS internal files like `external-context-creator.js`, indicating the framework attempted to execute resolver logic but encountered an exception that was not intercepted by the application code.GraphQL ProblemsgraphqlGraphQLErrorsnestjs
prequel-2025-0083
Medium
Impact: 7/10
Mitigation: 5/10
GraphQL schema validation failuresGraphQL validation errors occur when client requests fail to comply with the GraphQL schema. These errors typically happen during query parsing and validation phases, before execution begins. Common validation failures include unknown types, missing required arguments, incorrect field usage, or invalid input values. These errors prevent the operation from executing and return error messages that describe the validation problems to the client.API Service ProblemsgraphqlGraphQLValidationAPI Error