CVE-2023-49559 is a medium-severity (CVSS 5.3) CWE-770 vulnerability in github.com/vektah/gqlparser/v2. A fix is available for github.com/vektah/gqlparser/v2 — see the affected versions and patch details below.
gqlparser denial of service vulnerability via the parserDirectives function
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-49559.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/vektah/gqlparser/v2🐹github.com/vektah/gqlparserReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
An issue in vektah gqlparser open-source-library v.2.5.10 allows a remote attacker to cause a denial of service via a crafted script to the parserDirectives function.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/vektah/gqlparser/v2 | all versions | 2.5.14go get github.com/vektah/gqlparser/v2@v2.5.14 |
| 🐹Go | github.com/vektah/gqlparser | all versions | 2.5.14go get github.com/vektah/gqlparser@v2.5.14 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/vektah/gqlparser/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/vektah/gqlparser/v2 to 2.5.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49559 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2023-49559 in your dependencies?
Find it across Go, including transitive dependencies.