graphql-scalars PhoneNumber scalar is vulnerable to regular expression denial of service
Affects graphql-scalars 1.24.1 through 2.0.0 for servers that expose the PhoneNumber scalar on an argument, input object field or variable. Fixed in 2.0.1.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 2.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
The graphql-scalars library's PhoneNumber scalar, which validates phone number values in GraphQL schemas, is affected by this vulnerability. A specially crafted, unauthenticated request containing a long run of digits can make the server's Node.js process hang by blocking its event loop, causing a denial of service.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
GraphQL Scalars is a library of custom GraphQL scalars for creating precise type-safe GraphQL schemas. From 1.24.1 until 2.0.1, GraphQLPhoneNumber in src/scalars/PhoneNumber.ts uses ambiguous nested digit quantifiers that backtrack exponentially when a PhoneNumber value contains a run of digits followed by a character that makes the match fail. GraphQL evaluates parseLiteral during document validation and parseValue during variable coercion before resolver authentication or authorization, so a small unauthenticated request can block the Node.js event loop and stall the server process. serialize is also affected when unvalidated stored values are returned through the scalar. This issue is fixed in version 2.0.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- graphql-hive graphql-scalars
From 1.24.1 · fixed in 2.0.1
- graphql-scalarsnpm
From 1.24.1 · fixed in 2.0.1
References 4
GitHub · graphql-hive/graphql-scalars
Questions about CVE-2026-115887
What does this mean?
A small crafted PhoneNumber value blocks the Node.js event loop and stalls the server process. This is a regular expression denial of service (CWE-1333).Source: github.com
Am I affected, and how do I check?
graphql-scalars versions 1.24.1 through 2.0.0 are affected, and only when the schema exposes the PhoneNumber scalar on an argument, input object field or variable. To check, look up the graphql-scalars version in the project's lockfile or package.json and search the schema for PhoneNumber.Source: github.com
What should I do about it?
Upgrade graphql-scalars to 2.0.1, the first fixed version. Until then, the advisory's workaround is to run Node with --enable-experimental-regexp-engine-on-excessive-backtracks so V8 falls back to a linear-time engine.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data