VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/vektah/gqlparser/v2: vulnerability history, versions and safety

github.com/vektah/gqlparser/v2 is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/vektah/gqlparser/v2 vulnerabilities

Vulert verdict on github.com/vektah/gqlparser/v2 v2.5.64 i

Updated on 23 Oct 2026

Action needed: v2.5.64 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v2.5.64 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 12 Jun 2024 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Stars 559 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/vektah/gqlparser/v2, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v2.5.64 22 Oct 2026 M1 MIT Yes Details →
v2.5.64-0.20261022014128-b53051405131 22 Oct 2026 M1 MIT Yes Details →
v2.5.64-0.20261019214900-07488f82112b 19 Oct 2026 M1 MIT Yes Details →
v2.5.63 14 Oct 2026 M1 MIT Yes Details →
v2.5.63-0.20261010142511-d4ae1da86b71 10 Oct 2026 M1 MIT Yes Details →
v2.5.62 08 Oct 2026 M1 MIT Yes Details →
v2.5.61 07 Oct 2026 M1 MIT Yes Details →
v2.5.60 02 Oct 2026 M1 MIT Yes Details →
v2.5.60-0.20261002192521-4e17d6e4d0d9 02 Oct 2026 M1 MIT Yes Details →
v2.5.59 02 Oct 2026 M1 MIT Yes Details →
v2.5.58 23 Sep 2026 M1 MIT Yes Details →
v2.5.38-0.20260922021609-991cd110b7c4 22 Sep 2026 M1 MIT Yes Details →
v2.5.38-0.20260908012105-5d4af164a858 08 Sep 2026 M1 MIT Yes Details →
v2.5.37 31 Aug 2026 M1 MIT Yes Details →
v2.5.37-0.20260831191157-be64ed559a0a 31 Aug 2026 M1 MIT Yes Details →
v2.5.37-0.20260812170105-5adc5b2654eb 12 Aug 2026 M1 MIT Yes Details →
v2.5.37-0.20260807213019-62d1c292daf5 07 Aug 2026 M1 MIT Yes Details →
v2.5.37-0.20260801125152-a0f728e71d33 01 Aug 2026 M1 MIT Yes Details →
v2.5.37-0.20260706225355-fe9837d78a6e 06 Jul 2026 M1 MIT Yes Details →
v2.5.36 29 Jun 2026 M1 MIT Yes Details →
v2.5.36-0.20260629004210-8ad616fc357c 29 Jun 2026 M1 MIT Yes Details →
v2.5.35 19 Jun 2026 M1 MIT Yes Details →
v2.5.35-0.20260615175226-5112c6b64846 15 Jun 2026 M1 MIT Yes Details →
v2.5.34 06 Jun 2026 M1 MIT Yes Details →
v2.5.34-0.20260525182906-49ea8048c933 25 May 2026 M1 MIT Yes Details →
v2.5.34-0.20260509174440-9e555b834f9e 09 May 2026 M1 MIT Yes Details →
v2.5.34-0.20260430194749-84821cc710b5 30 Apr 2026 M1 MIT Yes Details →
v2.5.33 24 Apr 2026 M1 MIT Yes Details →
v2.5.33-0.20260401170116-021901042dbe 01 Apr 2026 M1 MIT Yes Details →
v2.5.33-0.20260331135016-be677085400f 31 Mar 2026 M1 MIT Yes Details →
v2.5.32 19 Feb 2026 M1 MIT Yes Details →
v2.5.32-0.20260203020306-7bb1b07fc886 03 Feb 2026 M1 MIT Yes Details →
v2.5.32-0.20251208212752-fae7dc34e271 08 Dec 2025 M1 MIT Yes Details →
v2.5.32-0.20251202202120-2545fd76ddc5 02 Dec 2025 M1 MIT Yes Details →
v2.5.32-0.20251124201620-f94515a4e6a5 24 Nov 2025 M1 MIT Yes Details →
v2.5.32-0.20251112003531-e535afd9a885 12 Nov 2025 M1 MIT Yes Details →
v2.5.31 30 Oct 2025 M1 MIT Yes Details →
v2.5.31-0.20251028104214-1bb503eb1308 28 Oct 2025 M1 MIT Yes Details →
v2.5.31-0.20250930171404-a6628019dde9 30 Sep 2025 M1 MIT Yes Details →
v2.5.31-0.20250914183228-343d05eb554e 14 Sep 2025 M1 MIT Yes Details →
v2.5.31-0.20250902113621-ac6687213145 02 Sep 2025 M1 MIT Yes Details →
v2.5.31-0.20250826105125-a13b5b87aa97 26 Aug 2025 M1 MIT Yes Details →
v2.5.31-0.20250819120333-99d3dc055bfe 19 Aug 2025 M1 MIT Yes Details →
v2.5.31-0.20250714224853-d6846857c574 14 Jul 2025 M1 MIT Yes Details →
v2.5.31-0.20250701144221-f13ad25f53b3 01 Jul 2025 M1 MIT Yes Details →
v2.5.31-0.20250701011413-c97f4f87beae 01 Jul 2025 M1 MIT Yes Details →
v2.5.30 28 Jun 2025 M1 MIT Yes Details →
v2.5.29 27 Jun 2025 M1 MIT Yes Details →
v2.5.29-0.20250624024535-9e14766b4d65 24 Jun 2025 M1 MIT Yes Details →
v2.5.28 15 Jun 2025 M1 MIT Yes Details →
v2.5.28-0.20250614135810-eadea450e33f 14 Jun 2025 M1 MIT Yes Details →
v2.5.28-0.20250603031645-f7a3835b263c 03 Jun 2025 M1 MIT Yes Details →
v2.5.28-0.20250513014029-7defefafbb21 13 May 2025 M1 MIT Yes Details →
v2.5.27 07 May 2025 M1 MIT Yes Details →
v2.5.27-0.20250505205118-fbff6f28e08f 05 May 2025 M1 MIT Yes Details →
v2.5.26 24 Apr 2025 M1 MIT Yes Details →
v2.5.26-0.20250419155812-539d990f1c0a 19 Apr 2025 M1 MIT Yes Details →
v2.5.25 17 Apr 2025 M1 MIT Yes Details →
v2.5.24 09 Apr 2025 M1 MIT Yes Details →
v2.5.24-0.20250325003455-762608a1926a 25 Mar 2025 M1 MIT Yes Details →
v2.5.24-0.20250318112433-c70447b63a05 18 Mar 2025 M1 MIT Yes Details →
v2.5.24-0.20250317202830-bec5c8e8ded9 17 Mar 2025 M1 MIT Yes Details →
v2.5.24-0.20250304115519-eab8c62a4cfa 04 Mar 2025 M1 MIT Yes Details →
v2.5.23 27 Feb 2025 M1 MIT Yes Details →
v2.5.23-0.20250224231641-94fb1f6ad8f6 24 Feb 2025 M1 MIT Yes Details →
v2.5.23-0.20250218024045-3899e7777d28 18 Feb 2025 M1 MIT Yes Details →
v2.5.23-0.20250210202229-c8b3d7bb2b3e 10 Feb 2025 M1 MIT Yes Details →
v2.5.23-0.20250203193251-a9517a55bf85 03 Feb 2025 M1 MIT Yes Details →
v2.5.23-0.20250128154144-23ba15b0c1c0 28 Jan 2025 M1 MIT Yes Details →
v2.5.23-0.20250127200112-28ef20ae1564 27 Jan 2025 M1 MIT Yes Details →
v2.5.22 27 Jan 2025 M1 MIT Yes Details →
v2.5.22-0.20250120203230-217e30410d10 20 Jan 2025 M1 MIT Yes Details →
v2.5.22-0.20250113235253-7f6e1d1dff33 13 Jan 2025 M1 MIT Yes Details →
v2.5.21 25 Dec 2024 M1 MIT Yes Details →
v2.5.21-0.20241210013943-6558e6f24f26 10 Dec 2024 M1 MIT Yes Details →
v2.5.20 26 Nov 2024 M1 MIT Yes Details →
v2.5.20-0.20241126142339-755d42bde5f3 26 Nov 2024 M1 MIT Yes Details →
v2.5.19 07 Nov 2024 M1 MIT Yes Details →
v2.5.19-0.20241107155253-b269ffc958fe 07 Nov 2024 M1 MIT Yes Details →
v2.5.19-0.20241029112704-e408be38fcd5 29 Oct 2024 M1 MIT Yes Details →
v2.5.19-0.20241025145842-89fc13751430 25 Oct 2024 M1 MIT Yes Details →
v2.5.19-0.20241017121149-6361a74e7f14 17 Oct 2024 M1 MIT Yes Details →
v2.5.18 16 Oct 2024 M1 MIT Yes Details →
v2.5.18-0.20241016111028-49df52f4730d 16 Oct 2024 M1 MIT Yes Details →
v2.5.18-0.20241015015912-fb9ca5a3bde5 15 Oct 2024 M1 MIT Yes Details →
v2.5.18-0.20241014104546-c888731918cc 14 Oct 2024 M1 MIT Yes Details →
v2.5.18-0.20241007214411-f0827b6cb201 07 Oct 2024 M1 MIT Yes Details →
v2.5.18-0.20241001004627-4eab08398dbc 01 Oct 2024 M1 MIT Yes Details →
v2.5.18-0.20240929173549-888baf888bf4 29 Sep 2024 M1 MIT Yes Details →
v2.5.17 26 Sep 2024 M1 MIT Yes Details →
v2.0.0-20240827104627-ed10d5c7e1d3 27 Aug 2024 M1 MIT Yes Details →
v2.5.17-0.20240827104627-ed10d5c7e1d3 27 Aug 2024 M1 MIT Yes Details →
v2.5.17-0.20240806104836-26ff39108826 06 Aug 2024 M1 MIT Yes Details →
v2.5.17-0.20240715193532-da27ce696e07 15 Jul 2024 M1 MIT Yes Details →
v2.5.17-0.20240618164157-162c9a441579 18 Jun 2024 M1 MIT Yes Details →
v2.5.17-0.20240614173635-832be1634009 14 Jun 2024 M1 MIT Yes Details →
v2.5.16 12 Jun 2024 M1 MIT Yes Details →
v2.5.15 12 Jun 2024 M1 MIT Yes Details →
v2.5.14 12 Jun 2024 M1 MIT Yes Details →
v2.5.13 11 Jun 2024 M1 MIT Yes Details →
v2.5.13-0.20240610220653-6db1bd39a014 10 Jun 2024 M1 — Yes Details →
v2.5.13-0.20240603205245-7c770f6a27ba 03 Jun 2024 M1 — Yes Details →
v2.5.13-0.20240527235121-0ed49739e85d 27 May 2024 M1 — Yes Details →
v2.5.12 16 May 2024 M1 — Yes Details →
v2.5.12-0.20240516211909-00fd36f5cfc7 16 May 2024 M1 — Yes Details →
v2.5.12-0.20240405110402-59e3c3a2e92c 05 Apr 2024 M1 — Yes Details →
v2.5.11 10 Jan 2024 M1 — Yes Details →
v2.5.11-0.20240110140828-591c98bb315b 10 Jan 2024 M1 — Yes Details →
v2.5.11-0.20240108194939-a94295433167 08 Jan 2024 M1 — Yes Details →
v2.5.11-0.20231019112842-bf1736ae2956 19 Oct 2023 M1 — Yes Details →
v2.5.11-0.20230927231331-e5a1b674bc55 27 Sep 2023 M1 — Yes Details →
v2.5.10 15 Sep 2023 M1 — Yes Details →
v2.5.10-0.20230915103723-88e2f8c30d44 15 Sep 2023 M1 — Yes Details →
v2.5.9 08 Sep 2023 M1 — Yes Details →
v2.5.9-0.20230907153233-f2809bd4a9f5 07 Sep 2023 M1 — Yes Details →
v2.5.9-0.20230907143609-c0a44fb18349 07 Sep 2023 M1 — Yes Details →
v2.5.8 17 Jul 2023 M1 — Yes Details →
v2.5.7 15 Jul 2023 M1 — Yes Details →
v2.5.7-0.20230712112815-4b44f9bff47d 12 Jul 2023 M1 — Yes Details →
v2.5.7-0.20230705200544-b8ec355296eb 05 Jul 2023 M1 — Yes Details →

The newest 120 of 190 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/vektah/gqlparser/v2

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in gqlparser 5.3 medium 2.5.14 12 Jun 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/vektah/gqlparser/v2

Is github.com/vektah/gqlparser/v2 safe to use?

Vulert records 1 vulnerabilities for github.com/vektah/gqlparser/v2 in Go: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/vektah/gqlparser/v2's Vulert package health score?

Vulert scores github.com/vektah/gqlparser/v2 81/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/vektah/gqlparser/v2 affected?

Yes. v2.5.64, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does github.com/vektah/gqlparser/v2 have?

1 vulnerability is recorded for github.com/vektah/gqlparser/v2 in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/vektah/gqlparser/v2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/vektah/gqlparser/v2 in the last 12 months, and the oldest entry in this database dates to 12 Jun 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/vektah/gqlparser/v2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/vektah/gqlparser/v2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/vektah/gqlparser/v2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.