graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 contains a denial of service vulnerability that allows unauthenticated attackers to bypass the parser max_tokens limit using long runs of comments. Attackers can submit GraphQL documents of consecutive comments that Lexer.lookahead fully tokenizes before limit checks, consuming CPU and memory proportional to document size.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Sun, 22 Nov 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 contains a denial of service vulnerability that allows unauthenticated attackers to bypass the parser max_tokens limit using long runs of comments. Attackers can submit GraphQL documents of consecutive comments that Lexer.lookahead fully tokenizes before limit checks, consuming CPU and memory proportional to document size. | |
| Title | graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 Denial of Service via Parser max_tokens Comment Runs | |
| First Time appeared |
Graphql
Graphql graphql |
|
| Weaknesses | CWE-770 | |
| CPEs | cpe:2.3:a:graphql:graphql:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Graphql
Graphql graphql |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-22T21:22:45.770Z
Reserved: 2026-11-22T17:09:32.785Z
Link: CVE-2026-134795
No data.
No data.
No data.
OpenCVE Enrichment
No data.
Weaknesses