Is github.com/vektah/gqlparser/v2 2.5 vulnerable?
Go · 45 releases from 2.5.0 to 2.5.64 · latest github.com/vektah/gqlparser/v2 is 2.5.64 · checked 18 Nov 2026
No known advisories in the last release
github.com/vektah/gqlparser/v2 2.5.64, the last 2.5 release, has no known advisories. 2 advisories affect earlier 2.5.x releases, so update to 2.5.64.
go get github.com/vektah/gqlparser/v2@v2.5.64Is your project on an affected github.com/vektah/gqlparser/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 2.5.x, affecting earlier releases
Denial of service vulnerability via the parseDirectives function in github.com/vektah/gqlparser
- Affected
- <2.5.14
- Fixed in
- 2.5.14
gqlparser denial of service vulnerability via the parserDirectives function
- Affected
- <2.5.14
- Fixed in
- 2.5.14
Every github.com/vektah/gqlparser/v2 2.5.x release
Affected: 2.5.0 to 2.5.13. 2.5.14 and later are not affected.
| Version | Known advisories |
|---|---|
| github.com/vektah/gqlparser/v2 2.5.64 | None |
| github.com/vektah/gqlparser/v2 2.5.63 | None |
| github.com/vektah/gqlparser/v2 2.5.62 | None |
| github.com/vektah/gqlparser/v2 2.5.61 | None |
| github.com/vektah/gqlparser/v2 2.5.60 | None |
| github.com/vektah/gqlparser/v2 2.5.59 | None |
| github.com/vektah/gqlparser/v2 2.5.58 | None |
| github.com/vektah/gqlparser/v2 2.5.37 | None |
| github.com/vektah/gqlparser/v2 2.5.36 | None |
| github.com/vektah/gqlparser/v2 2.5.35 | None |
| github.com/vektah/gqlparser/v2 2.5.34 | None |
| github.com/vektah/gqlparser/v2 2.5.33 | None |
| github.com/vektah/gqlparser/v2 2.5.32 | None |
| github.com/vektah/gqlparser/v2 2.5.31 | None |
| github.com/vektah/gqlparser/v2 2.5.30 | None |
| github.com/vektah/gqlparser/v2 2.5.29 | None |
| github.com/vektah/gqlparser/v2 2.5.28 | None |
| github.com/vektah/gqlparser/v2 2.5.27 | None |
| github.com/vektah/gqlparser/v2 2.5.26 | None |
| github.com/vektah/gqlparser/v2 2.5.25 | None |
| github.com/vektah/gqlparser/v2 2.5.24 | None |
| github.com/vektah/gqlparser/v2 2.5.23 | None |
| github.com/vektah/gqlparser/v2 2.5.22 | None |
| github.com/vektah/gqlparser/v2 2.5.21 | None |
| github.com/vektah/gqlparser/v2 2.5.20 | None |
| github.com/vektah/gqlparser/v2 2.5.19 | None |
| github.com/vektah/gqlparser/v2 2.5.18 | None |
| github.com/vektah/gqlparser/v2 2.5.17 | None |
| github.com/vektah/gqlparser/v2 2.5.16 | None |
| github.com/vektah/gqlparser/v2 2.5.15 | None |
| github.com/vektah/gqlparser/v2 2.5.14 | None |
| github.com/vektah/gqlparser/v2 2.5.13 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.12 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.11 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.10 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.9 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.8 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.7 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.6 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.5 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.4 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.3 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.2 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.1 | CVE-2023-49559, CVE-2023-49559 |
| github.com/vektah/gqlparser/v2 2.5.0 | CVE-2023-49559, CVE-2023-49559 |
Which of your client projects are still on github.com/vektah/gqlparser/v2 2.5?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/vektah/gqlparser/v2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/vektah/gqlparser/v2 versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.