VulnerabilityPublished 16 Jan 2026

CVE-2026-23735: graphql-modules · Race Condition

Affects graphql-modulesSource CVE Database V5

Not known to be exploited · CVSS 8.7 High : upgrade to 3.1.1 or 2.4.1 soon.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score

8.7High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.1.1, 2.4.1

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2026
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 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 graphql-modules and graphql-hive/graphql-modules to 3.1.1 or 2.4.1.

Affected software

Product	Affected	Fixed in
graphql-hivegraphql-modules	Affected >=2.2.1 <2.4.1 >=3.0.0 <3.1.1	Fixed in 3.1.1 2.4.1
GitHubgraphql-hive/graphql-modules`pkg:github/graphql-hive/graphql-modules`Other threats	Affected >=2.2.1 <2.4.1 >=3.0.0 <3.1.1	Fixed in 2.4.1 3.1.1

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

AI-suggested

European organizations should immediately identify any deployments of graphql-hive graphql-modules within the affected version ranges (>=2.2.1 and <2.4.1, >=3.0.0 and <3.1.1). The primary mitigation is to upgrade to patched versions 2.4.1 or 3.1.1 as soon as possible. If immediate upgrade is not feasible, organizations should implement strict request serialization or limit concurrency on services using @ExecutionContext() to reduce the risk of context mixing. Additionally, review and enhance logging and monitoring around GraphQL API requests to detect anomalous access patterns or context leakage. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to monitor and potentially block suspicious concurrent request patterns. Conduct thorough code reviews to ensure proper synchronization when handling shared resources in custom modules. Finally, enforce strict token scopes and short token lifetimes to minimize the impact of any leaked authentication context.

Description

CVE-2026-23735 is a high-severity race condition vulnerability in graphql-hive's graphql-modules versions 2.2.1 to before 2.4.1 and 3.0.0 to before 3.1.1. The flaw occurs when multiple parallel requests trigger the same service, causing request contexts—often containing sensitive authentication tokens—to be mixed up due to improper synchronization in the @ExecutionContext() injection.

Impact

For European organizations, this vulnerability poses a serious risk to the confidentiality and integrity of user data handled by GraphQL APIs using the affected graphql-modules versions. Since the flaw allows context leakage between concurrent requests, sensitive authentication tokens and user-specific information could be exposed or misused, leading to unauthorized data access or privilege escalation. This could result in data breaches, regulatory non-compliance (e.g., GDPR violations), reputational damage, and potential financial penalties. Organizations in sectors with high data sensitivity such as finance, healthcare, and government are particularly at risk. The vulnerability's ease of exploitation without authentication or user interaction increases the likelihood of automated attacks or exploitation by malicious insiders. Additionally, the shared resource race condition could cause inconsistent application behavior, impacting service reliability and availability indirectly. Given the widespread adoption of GraphQL in modern web services, the scope of affected systems across Europe could be substantial if unpatched.

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Jan 2026, 20:38 UTC

WeaknessesCWE-362

Technical details

References

Community reviews

Related threats