GHSA-733V-P3H5-QPQ7

A query cost restriction using the cost-limit can be bypassed if ignoreIntrospection is enabled (which is the default configuration) by naming your query/fragment __schema.

Details

At the start of the computeComplexity function, we have the following check for ignoreIntrospection option:

    if (this.config.ignoreIntrospection && 'name' in node && node.name?.value === '__schema') {
      return 0;
    }

However, the node can be FieldNode | FragmentDefinitionNode | InlineFragmentNode | OperationDefinitionNode | FragmentSpreadNode

So, for example, sending the following query

query hello {
  books {
    title
  }
}

would create an OperationDefinitionNode with node.name.value == 'hello'

The proper way to handle this would be to check for the __schema field, which would create a FieldNode.

The fix is

    if (
      this.config.ignoreIntrospection &&
      'name' in node &&
      node.name?.value === '__schema' &&
      node.kind === Kind.FIELD
    ) {
      return 0;
    }

to assert that the node must be a FieldNode

PoC

query  {
  ...__schema
}

fragment __schema on Query {
  books {
    title
    author
  }
}

query __schema {
  books {
    title
    author
  }
}

Applications using GraphQL Armor Cost Limit plugin with ignoreIntrospection enabled.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

GHSA-733V-P3H5-QPQ7 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.4.2); upgrading removes the vulnerable code path.

Kodem intelligence

Fixed on 772. A quick patch would be to set ignoreIntrospection to false.

1. What is GHSA-733V-P3H5-QPQ7? GHSA-733V-P3H5-QPQ7 is a medium-severity uncontrolled resource consumption vulnerability in @escape.tech/graphql-armor-cost-limit (npm), affecting versions < 2.4.2. It is fixed in 2.4.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is GHSA-733V-P3H5-QPQ7? GHSA-733V-P3H5-QPQ7 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @escape.tech/graphql-armor-cost-limit are affected by GHSA-733V-P3H5-QPQ7? @escape.tech/graphql-armor-cost-limit (npm) versions < 2.4.2 is affected.
4. Is there a fix for GHSA-733V-P3H5-QPQ7? Yes. GHSA-733V-P3H5-QPQ7 is fixed in 2.4.2. Upgrade to this version or later.
5. Is GHSA-733V-P3H5-QPQ7 exploitable, and should I be worried? Whether GHSA-733V-P3H5-QPQ7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-733V-P3H5-QPQ7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-733V-P3H5-QPQ7? Upgrade @escape.tech/graphql-armor-cost-limit to 2.4.2 or later.