VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/graphql-go/graphql: vulnerability history, versions and safety

github.com/graphql-go/graphql is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, first recorded in Aug 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
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/graphql-go/graphql vulnerabilities

Vulert verdict on github.com/graphql-go/graphql v0.8.1 i

Updated on 23 Oct 2026

Action needed: v0.8.1 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 74/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • 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 v0.8.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 23 Aug 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 10,141 i
  • OpenSSF scorecard 2/10 i
  • Last release 42 months ago 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/graphql-go/graphql, 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
v0.0.0-20260623012937-6acef3563ff7 23 Jun 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20260623012937-6acef3563ff7 23 Jun 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20260621165403-b22dee3978a2 21 Jun 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20260620153722-25aab32d96a0 20 Jun 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20260617013948-ec2560fb4958 17 Jun 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20260614223730-7cd8e416df55 14 Jun 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20260614193323-d40b3bdec942 14 Jun 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20260606201526-2e39e53f0e4f 06 Jun 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20260520151952-526d0f9207a6 20 May 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20260509182626-2d6136ab5052 09 May 2026 H1 U1 MIT Yes Details →
v0.8.2-0.20251227194222-d5f8f3c54f31 27 Dec 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20251226003758-76aa82bec42c 26 Dec 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20251220180731-3ca1f2d5ffb6 20 Dec 2025 H1 U1 MIT Yes Details →
v0.0.0-20250728114051-fd7999201870 28 Jul 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20250728114051-fd7999201870 28 Jul 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20250718191459-f2a7e55af5ff 18 Jul 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20250401165618-5a1a6bbd23f9 01 Apr 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20250331215529-fac9bd6f6e33 31 Mar 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20250328174202-58689e0742f2 28 Mar 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20250328173927-36368bbbf311 28 Mar 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20250111190536-9a8900cc1669 11 Jan 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20250111190231-15ed81699852 11 Jan 2025 H1 U1 MIT Yes Details →
v0.8.2-0.20241012201702-a546af7e957c 12 Oct 2024 H1 U1 MIT Yes Details →
v0.8.2-0.20240325032059-f2b39caf7c92 25 Mar 2024 H1 U1 MIT Yes Details →
v0.8.2-0.20230722025156-4ebf270b92df 22 Jul 2023 H1 U1 MIT Yes Details →
v0.8.2-0.20230720132606-f4d0f50ff351 20 Jul 2023 H1 U1 MIT Yes Details →
v0.0.0-20230410181229-a9741863816e 10 Apr 2023 H1 U1 MIT Yes Details →
v0.8.1 10 Apr 2023 H1 U1 MIT Yes Details →
v0.8.1-0.20230410181229-a9741863816e 10 Apr 2023 H1 U1 MIT Yes Details →
v0.8.1-0.20230410180526-2a6e1fffd82b 10 Apr 2023 H1 U1 MIT Yes Details →
v0.8.1-0.20230225214401-623f8864341b 25 Feb 2023 H1 U1 MIT Yes Details →
v0.7.10-0.20230225214244-c18e0b62ee6b 25 Feb 2023 H1 U1 MIT Yes Details →
v0.8.1-0.20230225165908-55311b187aa7 25 Feb 2023 H1 U1 MIT Yes Details →
v0.7.8-0.20221116144027-2ce8c8b2bad8 16 Nov 2022 H1 U1 MIT Yes Details →
v0.0.0-20220729221248-4188bd5b3877 29 Jul 2022 H1 U1 MIT Yes Details →
v0.8.1-0.20220729221248-4188bd5b3877 29 Jul 2022 H1 U1 MIT Yes Details →
v0.0.0-20220614210743-09272f350067 14 Jun 2022 H1 U1 MIT Yes Details →
v0.7.10-0.20220614210743-09272f350067 14 Jun 2022 H1 U1 MIT Yes Details →
v0.8.1-0.20220614210743-09272f350067 14 Jun 2022 H1 U1 MIT Yes Details →
v0.8.1-0.20220612223706-a300a61b2d56 12 Jun 2022 H1 U1 MIT Yes Details →
v0.7.10-0.20210821233355-f02a1c961028 21 Aug 2021 H1 U1 MIT Yes Details →
v0.8.0 21 Aug 2021 H1 U1 MIT Yes Details →
v0.7.10-0.20210411022516-8a92e977c10b 11 Apr 2021 H1 U1 MIT Yes Details →
v0.7.10-0.20210411021017-18f6ed0fa2ca 11 Apr 2021 H1 U1 MIT Yes Details →
v0.7.10-0.20210224003636-4ce4c9ae4cce 24 Feb 2021 H1 U1 MIT Yes Details →
v0.7.10-0.20210207011242-1a9db8859ef5 07 Feb 2021 H1 U1 MIT Yes Details →
v0.7.10-0.20210130175335-2a54235b4fca 30 Jan 2021 H1 U1 MIT Yes Details →
v0.7.10-0.20210102222259-62a7bb0a9839 02 Jan 2021 H1 U1 MIT Yes Details →
v0.7.10-0.20201222134638-0f4df509c296 22 Dec 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20201208110622-388f8a2d4f19 08 Dec 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20201122033050-ba29b7605154 22 Nov 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20201011213334-dd05d5e04e77 11 Oct 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20201010220753-279acebb3169 10 Oct 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20200912235719-f7f76d6f04fa 12 Sep 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20200820121535-7fe5fa14a863 20 Aug 2020 H1 U1 MIT Yes Details →
v0.7.9-0.20200820121535-7fe5fa14a863 20 Aug 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20200817033913-d6b7434614ec 17 Aug 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20200803094827-3846be5e1cc5 03 Aug 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20200625171605-9441c498a148 25 Jun 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20200625171109-65e43c9767bf 25 Jun 2020 H1 U1 MIT Yes Details →
v0.7.9-0.20200519101133-eb0fdaee1058 19 May 2020 H1 U1 MIT Yes Details →
v0.7.9-0.20200518180521-183515e8badf 18 May 2020 H1 U1 MIT Yes Details →
v0.7.9-0.20200518171612-1fc61f7f418c 18 May 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20200426202700-116f19d099aa 26 Apr 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20200318093722-b7c3a1a0edb9 18 Mar 2020 H1 U1 MIT Yes Details →
v0.7.10-0.20200309053829-d6ffa494f365 09 Mar 2020 H1 U1 MIT Yes Details →
v0.7.9 05 Feb 2020 H1 U1 MIT Yes Details →
v0.7.9-0.20200205045927-02caa8943d64 05 Feb 2020 H1 U1 MIT Yes Details →
v0.7.9-0.20200205010740-b6b24cf8db61 05 Feb 2020 H1 U1 MIT Yes Details →
v0.7.9-0.20200205010002-d92501231054 05 Feb 2020 H1 U1 MIT Yes Details →
v0.7.9-0.20191125031726-2e2b648ecbe4 25 Nov 2019 H1 U1 MIT Yes Details →
v0.7.9-0.20190923031620-5fa0612dc4df 23 Sep 2019 H1 U1 MIT Yes Details →
v0.7.9-0.20190917211114-f52d8fa99fdd 17 Sep 2019 H1 U1 MIT Yes Details →
v0.7.9-0.20190703194555-24963e0980d4 03 Jul 2019 H1 U1 MIT Yes Details →
v0.7.9-0.20190410152505-ce04d48b3005 10 Apr 2019 H1 U1 MIT Yes Details →
v0.7.9-0.20190410152451-2638bece06ee 10 Apr 2019 H1 U1 MIT Yes Details →
v0.0.0-20190403165646-199d20bbfed7 03 Apr 2019 H1 U1 MIT Yes Details →
v0.7.9-0.20190403165646-199d20bbfed7 03 Apr 2019 H1 U1 MIT Yes Details →
v0.7.9-0.20190402093006-bed865f04586 02 Apr 2019 H1 U1 MIT Yes Details →
v0.7.8 28 Mar 2019 H1 U1 MIT Yes Details →
v0.7.8-0.20190312025155-cc858c0da0c4 12 Mar 2019 H1 U1 MIT Yes Details →
v0.7.8-0.20190309233312-bf68c1b144f4 09 Mar 2019 H1 U1 MIT Yes Details →
v0.7.8-0.20190206122623-63adf013df5d 06 Feb 2019 H1 U1 MIT Yes Details →
v0.7.8-0.20190204183845-db6bc15feab1 04 Feb 2019 H1 U1 MIT Yes Details →
v0.7.8-0.20190102022204-acd9fcd03fbd 02 Jan 2019 H1 U1 MIT Yes Details →
v0.0.0-20181210000637-21fe71deb586 10 Dec 2018 H1 U1 MIT Yes Details →
v0.7.8-0.20181210000637-21fe71deb586 10 Dec 2018 H1 U1 MIT Yes Details →
v0.7.7 03 Dec 2018 H1 U1 MIT Yes Details →
v0.7.7-0.20181202233247-bfe0f60e87da 02 Dec 2018 H1 U1 MIT Yes Details →
v0.7.7-0.20181202224757-31bba0387922 02 Dec 2018 H1 U1 MIT Yes Details →
v0.0.0-20181122022739-993e01c14646 22 Nov 2018 H1 U1 MIT Yes Details →
v0.7.7-0.20181122022739-993e01c14646 22 Nov 2018 H1 U1 MIT Yes Details →
v0.7.7-0.20181116000838-be84dc706e02 16 Nov 2018 H1 U1 MIT Yes Details →
v0.7.7-0.20181024002544-d35d558066e2 24 Oct 2018 H1 U1 MIT Yes Details →
v0.0.0-20181016235712-a7e15c029841 16 Oct 2018 H1 U1 MIT Yes Details →
v0.7.7-0.20181016235712-a7e15c029841 16 Oct 2018 H1 U1 MIT Yes Details →
v0.7.7-0.20181012131722-27d83defb221 12 Oct 2018 H1 U1 MIT Yes Details →
v0.7.7-0.20181002134816-17eefeabaa7a 02 Oct 2018 H1 U1 MIT Yes Details →
v0.0.0-20180912000844-cc8e9a91d6b8 12 Sep 2018 H1 U1 MIT Yes Details →
v0.7.7-0.20180912000844-cc8e9a91d6b8 12 Sep 2018 H1 U1 MIT Yes Details →
v0.0.0-20180911152737-cd6ef8df8e2e 11 Sep 2018 H1 U1 — Yes Details →
v0.7.7-0.20180902014409-094d00f5a7e8 02 Sep 2018 H1 U1 — Yes Details →
v0.0.0-20180821232111-ef7caf8f070b 21 Aug 2018 H1 U1 — Yes Details →
v0.7.7-0.20180821232111-ef7caf8f070b 21 Aug 2018 H1 U1 — Yes Details →
v0.7.6 31 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180728203850-0403491d4b5b 28 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180726104518-986ca8bdbec0 26 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180724223617-2b97f4c8ac93 24 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180720035725-2800ba051d4c 20 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180719041157-086b3bf7dcce 19 Jul 2018 H1 U1 — Yes Details →
v0.0.0-20180717235650-bce6c5b4b8e2 17 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180717235650-bce6c5b4b8e2 17 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180713203717-7f9745ea0c9e 13 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180712002308-796d22335788 12 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180703180852-01fc4cf8f258 03 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180702172657-2f78272077f4 02 Jul 2018 H1 U1 — Yes Details →
v0.7.6-0.20180627210803-b3e0b80676e9 27 Jun 2018 H1 U1 — Yes Details →
v0.7.6-0.20180616230548-a32961ebec33 16 Jun 2018 H1 U1 — Yes Details →
v0.7.6-0.20180516223202-d324d873eee4 16 May 2018 H1 U1 — Yes Details →
v0.7.6-0.20180427125950-0e5e5185f035 27 Apr 2018 H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/graphql-go/graphql

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-37315: Infinite Recursion in graphql-go Type Definition Parser 7.5 high 0.8.1 02 Aug 2022
CVE-2022-37315: Infinite recursion in parser in github.com/graphql-go/graphql N/A unrated 0.8.1 23 Aug 2022

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/graphql-go/graphql

Is github.com/graphql-go/graphql safe to use?

Vulert records 2 vulnerabilities for github.com/graphql-go/graphql in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. 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/graphql-go/graphql's Vulert package health score?

Vulert scores github.com/graphql-go/graphql 74/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/graphql-go/graphql affected?

Yes. v0.8.1, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/graphql-go/graphql should I use?

v0.8.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/graphql-go/graphql have?

2 vulnerabilities are recorded for github.com/graphql-go/graphql in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/graphql-go/graphql vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/graphql-go/graphql in the last 12 months, and the oldest entry in this database dates to 02 Aug 2022. 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/graphql-go/graphql 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/graphql-go/graphql for upcoming vulnerabilities?

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