CVE-2026-115887: CWE-1333: Inefficient Regular Expression Complexity in graphql-hive graphql-scalars
Description
A high-severity vulnerability (CVE-2026-115887) exists in the graphql-scalars library used by graphql-hive, specifically in the GraphQLPhoneNumber scalar between versions 1.24.1 and before 2.0.1. The issue is caused by inefficient regular expression complexity leading to exponential backtracking when parsing certain phone number inputs. This can block the Node.js event loop and stall the server, resulting in a denial of service. The vulnerability affects parseLiteral, parseValue, and serialize functions. It is fixed in version 2.0.1.
CVSS v3.1
Score 7.5high
Affected software
graphql-hive
graphql-scalars
pkg:npm/graphql-hive/graphql-scalarsRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The graphql-scalars library's GraphQLPhoneNumber scalar (versions >=1.24.1 <2.0.1) uses ambiguous nested digit quantifiers in its regular expressions, which cause exponential backtracking when a phone number input contains a run of digits followed by a character that causes the match to fail. Because GraphQL evaluates parseLiteral during document validation and parseValue during variable coercion before authentication or authorization, an unauthenticated attacker can send a small crafted request that blocks the Node.js event loop, stalling the server process. The serialize function is also affected when returning unvalidated stored values. This denial-of-service vulnerability is addressed in version 2.0.1.
Potential Impact
An attacker can cause a denial of service by sending crafted GraphQL requests that trigger exponential backtracking in the regular expression used by the GraphQLPhoneNumber scalar. This stalls the Node.js event loop, effectively blocking the server from processing further requests. The vulnerability can be exploited without authentication due to the evaluation order of GraphQL parsing functions. There is no impact on confidentiality or integrity, only availability.
Mitigation Recommendations
Upgrade graphql-scalars to version 2.0.1 or later, where this issue is fixed. No other mitigations are indicated by the vendor advisory. Patch status is confirmed fixed in 2.0.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-23T19:37:27.176Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6adbd340d73cc49347c1eff4
Added to database: 10/23/2026, 21:36:00 UTC
Last enriched: 10/23/2026, 21:50:09 UTC
Last updated: 10/23/2026, 21:50:50 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.