CVE-2024-40094

CVE-2024-40094 is a high-severity allocation of resources without limits or throttling vulnerability in com.graphql-java:graphql-java (maven), affecting versions < 19.11. It is fixed in 19.11, 20.9, 21.5.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

GraphQL Java does not properly consider ExecutableNormalizedFields (ENFs) as part of preventing denial of service

GraphQL Java (aka graphql-java) before 21.5 does not properly consider ExecutableNormalizedFields (ENFs) as part of preventing denial of service via introspection queries. 20.9 and 19.11 are also fixed versions.

Impact

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2024-40094 has a CVSS score of 7.5 (High). 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 (19.11, 20.9, 21.5); upgrading removes the vulnerable code path.

Affected versions

com.graphql-java:graphql-java (< 19.11) com.graphql-java:graphql-java (>= 20.0, < 20.9) com.graphql-java:graphql-java (>= 21.0, < 21.5)

Security releases

com.graphql-java:graphql-java → 19.11 (maven) com.graphql-java:graphql-java → 20.9 (maven) com.graphql-java:graphql-java → 21.5 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

com.graphql-java:graphql-java to 19.11 or later; com.graphql-java:graphql-java to 20.9 or later; com.graphql-java:graphql-java to 21.5 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2024-40094? CVE-2024-40094 is a high-severity allocation of resources without limits or throttling vulnerability in com.graphql-java:graphql-java (maven), affecting versions < 19.11. It is fixed in 19.11, 20.9, 21.5. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
  2. How severe is CVE-2024-40094? CVE-2024-40094 has a CVSS score of 7.5 (High). 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 com.graphql-java:graphql-java are affected by CVE-2024-40094? com.graphql-java:graphql-java (maven) versions < 19.11 is affected.
  4. Is there a fix for CVE-2024-40094? Yes. CVE-2024-40094 is fixed in 19.11, 20.9, 21.5. Upgrade to this version or later.
  5. Is CVE-2024-40094 exploitable, and should I be worried? Whether CVE-2024-40094 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 CVE-2024-40094 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 CVE-2024-40094?
    • Upgrade com.graphql-java:graphql-java to 19.11 or later
    • Upgrade com.graphql-java:graphql-java to 20.9 or later
    • Upgrade com.graphql-java:graphql-java to 21.5 or later

Other vulnerabilities in com.graphql-java:graphql-java

Stop the waste.
Protect your environment with Kodem.