VulnerabilityPublished 30 Jul 2024Updated 20 Nov 2024

CVE-2024-40094: graphql-java

Affects graphql-javaSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 21.5 : update graphql-java when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 21.5, 20.9, 19.11

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade com.graphql-java/graphql-java to 21.5, 20.9 or 19.11.

Affected software

Product	Affected	Fixed in
Mavencom.graphql-java/graphql-java`pkg:maven/com.graphql-java/graphql-java`Other threats	Affected <19.11 >19.11 <20.9 >20.9 <21.5	Fixed in 19.11 20.9 21.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-40094, organizations should immediately upgrade graphql-java to one of the fixed versions: 21.5, 20.9, or 19.11. Applying these patches ensures that ExecutableNormalizedFields are properly handled, preventing abuse via introspection queries. Beyond patching, implement strict rate limiting on GraphQL endpoints to reduce the impact of potential abuse. Employ query complexity analysis and depth limiting to restrict overly complex or deeply nested queries that could strain server resources. Monitor API traffic for unusual patterns indicative of abuse, such as repeated introspection queries or spikes in query volume. Consider disabling introspection queries in production environments if not required, or restrict them to authenticated and authorized users only. Regularly review and update dependency management processes to ensure timely application of security patches. Finally, incorporate these mitigations into incident response plans to quickly detect and respond to potential exploitation attempts.

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.

Impact

The primary impact of CVE-2024-40094 is the potential for denial of service attacks against systems running vulnerable versions of graphql-java. Attackers can exploit this flaw remotely without authentication, allowing them to disrupt API services by sending crafted introspection queries that consume excessive server resources. This can lead to degraded performance, increased latency, or complete service outages, affecting the availability and integrity of the affected applications. Organizations relying on graphql-java for critical API endpoints may experience operational disruptions, customer dissatisfaction, and potential financial losses due to downtime. While the vulnerability does not expose sensitive data directly, the resulting service interruptions can indirectly impact business continuity and trust. The medium severity rating indicates that while the threat is serious, it is not as critical as vulnerabilities that allow remote code execution or data breaches. However, the ease of exploitation and the widespread use of graphql-java in modern web applications elevate the risk profile.

References

Community reviews

Loading reviews…