Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
MEDIUM severity

CVE-2024-40094 graphql-java

MEDIUMFix: graphql-java/graphql-java@97743bc

CVE-2024-40094 is a medium-severity (CVSS 5.3) vulnerability in com.graphql-java:graphql-java. 1 public exploit reference exists, so weaponization risk is real. A fix is available for com.graphql-java:graphql-java — see the affected versions and patch details below.

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

Also known asGHSA-h9mq-f6q5-6c8m
Published
Jul 30, 2024
Updated
Aug 12, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-40094.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2024-40094 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

3 pkgs affected
com.graphql-java:graphql-javacom.graphql-java:graphql-javacom.graphql-java:graphql-java

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.graphql-java:graphql-javaall versions19.11com.graphql-java:graphql-java:19.11
Mavencom.graphql-java:graphql-java20.0&&< 20.920.9com.graphql-java:graphql-java:20.9
Mavencom.graphql-java:graphql-java21.0&&< 21.521.5com.graphql-java:graphql-java:21.5
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.graphql-java:graphql-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.graphql-java:graphql-java to 19.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-40094 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-40094 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-40094. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Moderate: This flaw in GraphQL Java allows for a denial of service by enabling attackers to craft specific introspection queries that lead to excessive resource allocation. This can result in resource exhaustion and service unavailability in Red Hat products utilizing the affected library.

ProductFixed inAdvisory
Cryostat 3 on RHEL 8cryostat-tech-preview/cryostat-db-rhel8:3.0.1-5RHSA-2024:8329
Red Hat build of Quarkus 3.2com.graphql-java.graphql-javaRHSA-2024:7676
Red Hat build of Quarkus 3.8com.graphql-java.graphql-javaRHSA-2024:7670
RHOSS-1.35-RHEL-8openshift-serverless-1/logic-data-index-ephemeral-rhel8:1.35.0-5RHSA-2025:0664

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-40094 in your dependencies?

O3 Security finds CVE-2024-40094 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2024-40094: graphql-java (Medium 5.3) | O3 Security