Vulnerability Database · Go · Package report

github.com/nats-io/jwt/v2: vulnerability history, versions and safety

github.com/nats-io/jwt/v2 is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Feb 2022. 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/nats-io/jwt/v2 v2.8.2 i

Updated on 23 Oct 2026

Action needed: v2.8.2 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 69/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • 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.8.2 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 15 Feb 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 90 i
  • OpenSSF scorecard 3/10 i
  • Last release 4 months ago i
  • Licence Apache-2.0 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/nats-io/jwt/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.0.0-20260602135338-82017236da50 02 Jun 2026 H1 Apache-2.0 Yes Details →
v2.8.2 02 Jun 2026 H1 Apache-2.0 Yes Details →
v2.0.0-20260602132544-071a1dedb58e 02 Jun 2026 H1 Apache-2.0 Yes Details →
v2.8.2-0.20260602132544-071a1dedb58e 02 Jun 2026 H1 Apache-2.0 Yes Details →
v2.0.0-20260312162627-1e990c9a58a8 12 Mar 2026 H1 Apache-2.0 Yes Details →
v2.8.1 12 Mar 2026 H1 Apache-2.0 Yes Details →
v2.8.1-0.20260312162627-1e990c9a58a8 12 Mar 2026 H1 Apache-2.0 Yes Details →
v2.8.1-0.20260311191306-e6531afcdfe8 11 Mar 2026 H1 Apache-2.0 Yes Details →
v2.0.0-20260303145926-169803d1a50f 03 Mar 2026 H1 Apache-2.0 Yes Details →
v2.8.1-0.20260303145926-169803d1a50f 03 Mar 2026 H1 Apache-2.0 Yes Details →
v2.0.0-20260227220012-e4173126b32a 27 Feb 2026 H1 Apache-2.0 Yes Details →
v2.8.1-0.20260227220012-e4173126b32a 27 Feb 2026 H1 Apache-2.0 Yes Details →
v2.8.1-0.20251114161926-adf3daff28cc 14 Nov 2025 H1 Apache-2.0 Yes Details →
v2.0.0-20250808141841-a2c583b4f371 08 Aug 2025 H1 Apache-2.0 Yes Details →
v2.8.0 08 Aug 2025 H1 Apache-2.0 Yes Details →
v2.7.5-0.20250806192437-7fdd66f0d939 06 Aug 2025 H1 Apache-2.0 Yes Details →
v2.7.5-0.20250806170630-0964917d2568 06 Aug 2025 H1 Apache-2.0 Yes Details →
v2.7.4 16 Apr 2025 H1 Apache-2.0 Yes Details →
v2.7.4-0.20241219171044-13f7264e0ea0 19 Dec 2024 H1 Apache-2.0 Yes Details →
v2.7.3 13 Dec 2024 H1 Apache-2.0 Yes Details →
v2.7.3-0.20241126234803-5297029e9786 26 Nov 2024 H1 Apache-2.0 Yes Details →
v2.6.1-0.20241009193556-f9c7776a4133 09 Oct 2024 H1 Apache-2.0 Yes Details →
v2.7.1 09 Oct 2024 H1 Apache-2.0 Yes Details →
v2.7.1-0.20241009193556-f9c7776a4133 09 Oct 2024 H1 Apache-2.0 Yes Details →
v2.7.2 09 Oct 2024 H1 Apache-2.0 Yes Details →
v2.7.1-0.20241009155308-64888e971feb 09 Oct 2024 H1 Apache-2.0 Yes Details →
v2.6.1-0.20241003195204-3ddc60d649e3 03 Oct 2024 H1 Apache-2.0 Yes Details →
v2.7.1-0.20241003195204-3ddc60d649e3 03 Oct 2024 H1 Apache-2.0 Yes Details →
v2.6.1-0.20241002211827-132f02c57839 02 Oct 2024 H1 Apache-2.0 Yes Details →
v2.7.1-0.20241002211827-132f02c57839 02 Oct 2024 H1 Apache-2.0 Yes Details →
v2.7.1-0.20241001214454-74c88303eeed 01 Oct 2024 H1 Apache-2.0 Yes Details →
v2.7.1-0.20241001190707-e5da71444547 01 Oct 2024 H1 Apache-2.0 Yes Details →
v2.7.1-0.20241001165941-a8b5dfe63b01 01 Oct 2024 H1 Apache-2.0 Yes Details →
v2.6.1-0.20240926181435-fbaa1547d7af 26 Sep 2024 H1 Apache-2.0 Yes Details →
v2.7.1-0.20240926181435-fbaa1547d7af 26 Sep 2024 H1 Apache-2.0 Yes Details →
v2.7.1-0.20240926175242-c69471de2a31 26 Sep 2024 H1 Apache-2.0 Yes Details →
v2.6.1-0.20240917153241-18a60d6f7f84 17 Sep 2024 H1 Apache-2.0 Yes Details →
v2.7.0 17 Sep 2024 H1 Apache-2.0 Yes Details →
v2.6.1-0.20240917143920-d3fa85bd725f 17 Sep 2024 H1 Apache-2.0 Yes Details →
v2.6.1-0.20240917140922-de1f16b5781c 17 Sep 2024 H1 Apache-2.0 Yes Details →
v2.6.1-0.20240913162803-2d9ece2f3a7a 13 Sep 2024 H1 Apache-2.0 Yes Details →
v2.6.1-0.20240912200904-90d24c5a61af 12 Sep 2024 H1 Apache-2.0 Yes Details →
v2.5.9-0.20240910221729-4445fcd6be06 10 Sep 2024 H1 Apache-2.0 Yes Details →
v2.6.0 10 Sep 2024 H1 Apache-2.0 Yes Details →
v2.5.9-0.20240910093232-2e1251e51094 10 Sep 2024 H1 Apache-2.0 Yes Details →
v2.5.9-0.20240910092522-bc9fb5fb3c2f 10 Sep 2024 H1 Apache-2.0 Yes Details →
v2.5.9-0.20240801130136-270cc45c44ee 01 Aug 2024 H1 Apache-2.0 Yes Details →
v2.5.9-0.20240730132529-79732145f9be 30 Jul 2024 H1 Apache-2.0 Yes Details →
v2.5.8 05 Jul 2024 H1 Apache-2.0 Yes Details →
v2.5.8-0.20240705143112-ff68a3bc6bb7 05 Jul 2024 H1 Apache-2.0 Yes Details →
v2.5.7 09 May 2024 H1 Apache-2.0 Yes Details →
v2.5.7-0.20240509160851-41dad79143e9 09 May 2024 H1 Apache-2.0 Yes Details →
v2.5.7-0.20240507172914-6b33489b89ba 07 May 2024 H1 Apache-2.0 Yes Details →
v2.5.6 18 Apr 2024 H1 Apache-2.0 Yes Details →
v2.5.6-0.20240418150938-1f3ff3245e5e 18 Apr 2024 H1 Apache-2.0 Yes Details →
v2.5.5 22 Feb 2024 H1 Apache-2.0 Yes Details →
v2.5.5-0.20240222165727-c2d30e2ffc63 22 Feb 2024 H1 Apache-2.0 Yes Details →
v2.5.5-0.20240222160411-13f2b0c94636 22 Feb 2024 H1 Apache-2.0 Yes Details →
v2.5.5-0.20240216210739-38e07c55c548 16 Feb 2024 H1 Apache-2.0 Yes Details →
v2.5.4 15 Feb 2024 H1 Apache-2.0 Yes Details →
v2.5.4-0.20240215165643-ed3fbfa49a16 15 Feb 2024 H1 Apache-2.0 Yes Details →
v2.5.4-0.20240214164243-40f01dce329c 14 Feb 2024 H1 Apache-2.0 Yes Details →
v2.5.4-0.20231220104856-f923b10c0be0 20 Dec 2023 H1 Apache-2.0 Yes Details →
v2.5.3 31 Oct 2023 H1 Apache-2.0 Yes Details →
v2.5.3-0.20231031161548-457367366f2f 31 Oct 2023 H1 Apache-2.0 Yes Details →
v2.5.3-0.20231024223625-012e7a3a42dc 24 Oct 2023 H1 Apache-2.0 Yes Details →
v2.5.3-0.20231024221234-2810af66e796 24 Oct 2023 H1 Apache-2.0 Yes Details →
v2.0.0-20230918155219-4b4f5502a8b3 18 Sep 2023 H1 Apache-2.0 Yes Details →
v2.5.2 18 Sep 2023 H1 Apache-2.0 Yes Details →
v2.5.2-0.20230918155219-4b4f5502a8b3 18 Sep 2023 H1 Apache-2.0 Yes Details →
v2.5.1 21 Aug 2023 H1 Apache-2.0 Yes Details →
v2.5.1-0.20230821203834-a3a24780d2f2 21 Aug 2023 H1 Apache-2.0 Yes Details →
v2.5.1-0.20230821202427-44fe206dcc26 21 Aug 2023 H1 Apache-2.0 Yes Details →
v2.5.0 21 Aug 2023 H1 Apache-2.0 Yes Details →
v2.0.0-20230324160218-535a7674fb61 24 Mar 2023 H1 Apache-2.0 Yes Details →
v2.4.1 24 Mar 2023 H1 Apache-2.0 Yes Details →
v2.4.1-0.20230324132415-dbd58c044047 24 Mar 2023 H1 Apache-2.0 Yes Details →
v2.4.1-0.20230323205815-2d45a0eae4ff 23 Mar 2023 H1 Apache-2.0 Yes Details →
v2.0.0-20230316214509-11e1fdb14153 16 Mar 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230316214509-11e1fdb14153 16 Mar 2023 H1 Apache-2.0 Yes Details →
v2.4.0 16 Mar 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230316212827-e3e39d66ad1c 16 Mar 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230313184310-f333f8d960ea 13 Mar 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230311161135-e7e361998bde 11 Mar 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230306212732-18caa555eb65 06 Mar 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230217195706-f72ebb5b11ab 17 Feb 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230215185859-8d1c62fe17b1 15 Feb 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230215184909-f135d4a5a6f9 15 Feb 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230210204924-fa6e649dfdef 10 Feb 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230208201144-3a4c73807749 08 Feb 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20230207205100-cf33d49680c1 07 Feb 2023 H1 Apache-2.0 Yes Details →
v2.3.1-0.20221227170542-bdf40fa3627b 27 Dec 2022 H1 Apache-2.0 Yes Details →
v2.3.1-0.20221226224525-146945d1bedc 26 Dec 2022 H1 Apache-2.0 Yes Details →
v2.3.1-0.20221214233435-ff7baa9e5e73 14 Dec 2022 H1 Apache-2.0 Yes Details →
v2.3.1-0.20221206125146-a07c95dfa9e1 06 Dec 2022 H1 Apache-2.0 Yes Details →
v2.3.1-0.20221205230255-ec09c3a122ff 05 Dec 2022 H1 Apache-2.0 Yes Details →
v2.3.1-0.20221205144435-160687f72d2d 05 Dec 2022 H1 Apache-2.0 Yes Details →
v2.3.1-0.20221203161016-18a62a065e6a 03 Dec 2022 H1 Apache-2.0 Yes Details →
v2.3.1-0.20221202180456-83b58fd54838 02 Dec 2022 H1 Apache-2.0 Yes Details →
v2.3.1-0.20221202141117-31baa5546134 02 Dec 2022 H1 Apache-2.0 Yes Details →
v2.0.0-20221202140421-bf796004f40f 02 Dec 2022 H1 — Yes Details →
v2.3.1-0.20221201232432-ca3be3cbd866 01 Dec 2022 H1 — Yes Details →
v2.3.0 28 Jun 2022 H1 — Yes Details →
v2.2.1-0.20220509180118-3bcd719cc7d0 09 May 2022 H1 — Yes Details →
v2.2.1-0.20220509165955-b7cabf8dbe60 09 May 2022 H1 — Yes Details →
v2.2.1-0.20220502184249-7544ab4a3bb0 02 May 2022 H1 — Yes Details →
v2.2.1-0.20220429175140-9f4f1d5cc977 29 Apr 2022 H1 — Yes Details →
v2.2.1-0.20220408195310-3b8532b48b96 08 Apr 2022 H1 — Yes Details →
v2.2.1-0.20220330180145-442af02fd36a 30 Mar 2022 H1 — Yes Details →
v2.2.1-0.20220328222144-5efd4536dd5c 28 Mar 2022 H1 — Yes Details →
v2.2.1-0.20220323195037-3472a33220ba 23 Mar 2022 H1 — Yes Details →
v2.2.1-0.20220323010931-b65a1fb60b29 23 Mar 2022 H1 — Yes Details →
v2.2.1-0.20220314192352-a4dc57f25ef3 14 Mar 2022 H1 — Yes Details →
v2.2.1-0.20220308021258-cfe08436740f 08 Mar 2022 H1 — Yes Details →
v2.2.1-0.20220307183908-70db6974fbdb 07 Mar 2022 H1 — Yes Details →
v2.2.1-0.20220216230343-0ebff70bb096 16 Feb 2022 H1 — Yes Details →
v2.2.1-0.20220216192239-c9f0ca9fcf07 16 Feb 2022 H1 — Yes Details →
v2.2.1-0.20220208174425-4b4a1c85619d 08 Feb 2022 H1 — Yes Details →
v2.2.1-0.20220113022732-58e87895b296 13 Jan 2022 H1 — Yes Details →
v2.2.1-0.20211214201657-b87bc9cf336d 14 Dec 2021 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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/nats-io/jwt/v2

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/nats-io/jwt/v2

Is github.com/nats-io/jwt/v2 safe to use?

Vulert records 1 vulnerabilities for github.com/nats-io/jwt/v2 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/nats-io/jwt/v2's Vulert package health score?

Vulert scores github.com/nats-io/jwt/v2 69/100, which reads as usable, but worth attention. 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/nats-io/jwt/v2 affected?

Yes. v2.8.2, 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/nats-io/jwt/v2 should I use?

v2.8.2 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/nats-io/jwt/v2 have?

1 vulnerability is recorded for github.com/nats-io/jwt/v2 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/nats-io/jwt/v2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/nats-io/jwt/v2 in the last 12 months, and the oldest entry in this database dates to 15 Feb 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/nats-io/jwt/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/nats-io/jwt/v2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/nats-io/jwt/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.