Vulnerability Database · Go · Package report

github.com/nghttp2/nghttp2: vulnerability history, versions and safety

github.com/nghttp2/nghttp2 is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Oct 2023. 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 H1
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.

Vulert verdict on github.com/nghttp2/nghttp2 v1.70.0 i

Updated on 23 Oct 2026

Action needed: v1.70.0 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 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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 v1.70.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 10 Oct 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 5,068 i
  • OpenSSF scorecard 6/10 i
  • Last release 2 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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/nghttp2/nghttp2, 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
v1.70.1-0.20261013155327-7e10fcf3c58e 13 Oct 2026 H1 MIT Yes Details →
v1.70.1-0.20261003141727-7a6d122aac52 03 Oct 2026 H1 MIT Yes Details →
v1.70.1-0.20260924232942-ea02d8bc7d15 24 Sep 2026 H1 MIT Yes Details →
v1.70.1-0.20260913072351-140157a8d751 13 Sep 2026 H1 MIT Yes Details →
v1.70.1-0.20260818091846-b6729c46cf13 18 Aug 2026 H1 MIT Yes Details →
v1.70.1-0.20260729120234-0fad0fda52a0 29 Jul 2026 H1 MIT Yes Details →
v1.70.0 29 Jul 2026 H1 MIT Yes Details →
v1.69.1-0.20260715150907-91a2c9c1bbb1 15 Jul 2026 H1 MIT Yes Details →
v1.69.1-0.20260701155643-1b3f1e9de182 01 Jul 2026 H1 MIT Yes Details →
v1.69.1-0.20260419090752-4944ae624af9 19 Apr 2026 H1 MIT Yes Details →
v1.69.0 19 Apr 2026 H1 MIT Yes Details →
v1.68.1-0.20260318160706-5c947628d53f 18 Mar 2026 H1 MIT Yes Details →
v1.68.1 18 Mar 2026 H1 MIT Yes Details →
v1.68.1-0.20260318100450-310c23981711 18 Mar 2026 H1 MIT Yes Details →
v1.68.1-0.20260317135032-5c7df8fa815a 17 Mar 2026 H1 MIT Yes Details →
v1.68.1-0.20251114102900-b485a87b57c7 14 Nov 2025 H1 MIT Yes Details →
v1.68.1-0.20251111124022-14c02f6bc3b2 11 Nov 2025 H1 MIT Yes Details →
v1.68.1-0.20251109114927-9b0044d05148 09 Nov 2025 H1 MIT Yes Details →
v1.68.1-0.20251027233337-3fa6a6349c37 27 Oct 2025 H1 MIT Yes Details →
v1.68.1-0.20251025083456-0e9d325deea4 25 Oct 2025 H1 MIT Yes Details →
v0.0.0-20251025081335-534b74b72524 25 Oct 2025 H1 MIT Yes Details →
v1.68.0 25 Oct 2025 H1 MIT Yes Details →
v1.67.1-0.20251022122539-a2667a669243 22 Oct 2025 H1 MIT Yes Details →
v0.0.0-20250919140053-b815972b0323 19 Sep 2025 H1 MIT Yes Details →
v1.64.1-0.20250919140053-b815972b0323 19 Sep 2025 H1 MIT Yes Details →
v1.67.1-0.20250919140053-b815972b0323 19 Sep 2025 H1 MIT Yes Details →
v0.0.0-20250919115927-59b6d0d1d9e9 19 Sep 2025 H1 MIT Yes Details →
v1.67.1-0.20250919115927-59b6d0d1d9e9 19 Sep 2025 H1 MIT Yes Details →
v1.67.1 15 Sep 2025 H1 MIT Yes Details →
v1.67.0 02 Sep 2025 H1 MIT Yes Details →
v0.0.0-20250617095600-ac22e0efe3f8 17 Jun 2025 H1 MIT Yes Details →
v1.66.0 17 Jun 2025 H1 MIT Yes Details →
v0.0.0-20250302071856-319bf015de8f 02 Mar 2025 H1 MIT Yes Details →
v1.65.0 02 Mar 2025 H1 MIT Yes Details →
v0.0.0-20250218101438-1049ce0a99b1 18 Feb 2025 H1 MIT Yes Details →
v1.64.0 21 Oct 2024 H1 MIT Yes Details →
v1.63.0 27 Aug 2024 H1 MIT Yes Details →
v1.62.1 19 May 2024 H1 MIT Yes Details →
v1.62.0 13 May 2024 H1 MIT Yes Details →
v1.61.0 04 Apr 2024 H1 MIT Yes Details →
v1.60.1-0.20240320082508-29b87d543410 20 Mar 2024 H1 MIT Yes Details →
v1.60.0 01 Mar 2024 H1 MIT Yes Details →
v1.59.0 21 Jan 2024 H1 MIT Yes Details →
v1.58.0 27 Oct 2023 H1 MIT Yes Details →
v1.57.0 10 Oct 2023 H1 MIT Yes Details →
v1.56.1-0.20230904093243-b7f98539687d 04 Sep 2023 H1 MIT Yes Details →
v1.56.0 04 Sep 2023 H1 MIT Yes Details →
v1.55.1 14 Jul 2023 H1 MIT Yes Details →
v1.55.1-0.20230712090628-82fc1163c6fd 12 Jul 2023 H1 MIT Yes Details →
v1.55.0 12 Jul 2023 H1 MIT Yes Details →
v1.54.1-0.20230608113141-2c955ab76b42 08 Jun 2023 H1 MIT Yes Details →
v1.54.0 07 Jun 2023 H1 MIT Yes Details →
v1.53.0 10 May 2023 H1 MIT Yes Details →
v1.52.0 13 Feb 2023 H1 MIT Yes Details →
v1.51.0 13 Nov 2022 H1 MIT Yes Details →
v1.50.0 21 Sep 2022 H1 MIT Yes Details →
v1.49.0 22 Aug 2022 H1 MIT Yes Details →
v1.48.0 23 Jun 2022 H1 MIT Yes Details →
v1.47.0 23 Feb 2022 H1 MIT Yes Details →
v1.46.1-0.20220101142159-e1446fd57a4a 01 Jan 2022 H1 MIT Yes Details →
v1.46.1-0.20211219114445-02e6cad1210f 19 Dec 2021 H1 MIT Yes Details →
v1.46.1-0.20211212141610-c3c0403dfaae 12 Dec 2021 H1 MIT Yes Details →
v0.0.0-20211103122326-c4828dbd7cc1 03 Nov 2021 H1 MIT Yes Details →
v1.46.1-0.20211103122326-c4828dbd7cc1 03 Nov 2021 H1 MIT Yes Details →
v0.0.0-20211030090918-0d16db2c65d8 30 Oct 2021 H1 MIT Yes Details →
v1.46.0 19 Oct 2021 H1 MIT Yes Details →
v1.45.1 21 Sep 2021 H1 MIT Yes Details →
v1.45.0 20 Sep 2021 H1 MIT Yes Details →
v1.44.0 18 Jul 2021 H1 MIT Yes Details →
v1.43.0 02 Feb 2021 H1 MIT Yes Details →
v1.42.0 23 Nov 2020 H1 MIT Yes Details →
v1.41.0 02 Jun 2020 H1 MIT Yes Details →
v1.40.0 15 Nov 2019 H1 MIT Yes Details →
v1.39.1-0.20190819132732-f2fde180cdcc 19 Aug 2019 H1 MIT Yes Details →
v1.39.2 13 Aug 2019 H1 MIT Yes Details →
v1.39.1 11 Jun 2019 H1 MIT Yes Details →
v1.39.0 11 Jun 2019 H1 MIT Yes Details →
v1.38.0 18 Apr 2019 H1 MIT Yes Details →
v1.37.0 07 Mar 2019 H1 MIT Yes Details →
v1.36.0 18 Jan 2019 H1 MIT Yes Details →
v1.35.1 09 Dec 2018 H1 MIT Yes Details →
v1.35.0 23 Nov 2018 H1 MIT Yes Details →
v1.34.0 04 Oct 2018 H1 MIT Yes Details →
v1.33.0 02 Sep 2018 H1 MIT Yes Details →
v1.32.1 25 Aug 2018 H1 MIT Yes Details →
v1.32.1-0.20180609072743-e5b3f9addd49 09 Jun 2018 H1 MIT Yes Details →
v1.32.0 08 May 2018 H1 MIT Yes Details →
v1.31.1 07 Apr 2018 H1 MIT Yes Details →
v1.31.0 27 Feb 2018 H1 MIT Yes Details →
v1.30.0 02 Feb 2018 H1 MIT Yes Details →
v1.29.0 19 Dec 2017 H1 MIT Yes Details →
v1.28.0 25 Nov 2017 H1 MIT Yes Details →
v1.27.0 24 Oct 2017 H1 MIT Yes Details →
v1.26.0 20 Sep 2017 H1 MIT Yes Details →
v1.25.0 18 Aug 2017 H1 MIT Yes Details →
v1.24.0 02 Jul 2017 H1 MIT Yes Details →
v1.23.1 30 May 2017 H1 MIT Yes Details →
v1.23.0 26 May 2017 H1 MIT Yes Details →
v1.22.0 24 Apr 2017 H1 MIT Yes Details →
v1.21.1 09 Apr 2017 H1 MIT Yes Details →
v1.21.0 27 Mar 2017 H1 — Yes Details →
v1.20.0 26 Feb 2017 H1 — Yes Details →
v1.19.0 25 Jan 2017 H1 — Yes Details →
v1.18.1 05 Jan 2017 H1 — Yes Details →
v1.18.0 27 Dec 2016 H1 — Yes Details →
v1.17.0 27 Nov 2016 H1 — Yes Details →
v1.16.1 13 Nov 2016 H1 — Yes Details →
v1.16.0 24 Oct 2016 H1 — Yes Details →
v1.15.0 25 Sep 2016 H1 — Yes Details →
v1.14.1 10 Sep 2016 H1 — Yes Details →
v1.14.0 25 Aug 2016 H1 — Yes Details →
v1.13.0 21 Jul 2016 H1 — Yes Details →
v1.12.0 26 Jun 2016 H1 — Yes Details →
v1.11.1 29 May 2016 H1 — Yes Details →
v1.11.0 26 May 2016 H1 — Yes Details →
v1.10.0 25 Apr 2016 H1 — Yes Details →
v1.9.2 03 Apr 2016 H1 — Yes Details →
v1.9.1 27 Mar 2016 H1 — Yes Details →
v1.9.0 26 Mar 2016 H1 — Yes Details →
v1.8.0 25 Feb 2016 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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/nghttp2/nghttp2

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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/nghttp2/nghttp2

Is github.com/nghttp2/nghttp2 safe to use?

Vulert records 1 vulnerabilities for github.com/nghttp2/nghttp2 in Go: 0 critical, 1 high, 0 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/nghttp2/nghttp2's Vulert package health score?

Vulert scores github.com/nghttp2/nghttp2 87/100, which reads as healthy. 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/nghttp2/nghttp2 affected?

Yes. v1.70.0, 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.

Which version of github.com/nghttp2/nghttp2 should I use?

v1.70.0 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/nghttp2/nghttp2 have?

1 vulnerability is recorded for github.com/nghttp2/nghttp2 in the Go ecosystem: 0 critical, 1 high, 0 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/nghttp2/nghttp2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/nghttp2/nghttp2 in the last 12 months, and the oldest entry in this database dates to 10 Oct 2023. 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/nghttp2/nghttp2 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/nghttp2/nghttp2 for upcoming vulnerabilities?

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