graphql-hive graphql-modules up to 2.4.0/3.1.0 ExecutionContext race condition

Summaryinfo

A vulnerability classified as critical was found in graphql-hive graphql-modules up to 2.4.0/3.1.0. This affects the function ExecutionContext. Such manipulation leads to race condition. This vulnerability is traded as CVE-2026-23735. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in graphql-hive graphql-modules up to 2.4.0/3.1.0. It has been rated as critical. Affected by this issue is the function ExecutionContext. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence 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 that is operating concurrently. Impacted is confidentiality, integrity, and availability. CVE summarizes:

GraphQL Modules is a toolset of libraries and guidelines dedicated to create reusable, maintainable, testable and extendable modules out of your GraphQL server. From 2.2.1 to before 2.4.1 and 3.1.1, when 2 or more parallel requests are made which trigger the same service, the context of the requests is mixed up in the service when the context is injected via @ExecutionContext(). ExecutionContext is often used to pass authentication tokens from incoming requests to services loading data from backend APIs. This vulnerability is fixed in 2.4.1 and 3.1.1.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-23735 since 01/15/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.

Upgrading to version 2.4.1 or 3.1.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• graphql-hive

Name

• graphql-modules

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4.0
• 3.0
• 3.1.0

Website

• Product: https://github.com/graphql-hive/graphql-modules/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion