VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/golang-jwt/jwt: vulnerability history, versions and safety

github.com/golang-jwt/jwt is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 88 releases, first recorded in Mar 2025. 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 U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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/golang-jwt/jwt vulnerabilities

Vulert verdict on github.com/golang-jwt/jwt v3.2.2+incompatible i

Updated on 23 Oct 2026

Careful: v3.2.2+incompatible has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v3.2.2+incompatible — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 26 Mar 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 9,247 i
  • OpenSSF scorecard 5/10 i
  • Last release 62 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/golang-jwt/jwt, 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
v4.5.1-0.20230523063856-7db667f8b3aa+incompatible 23 May 2023 U1 — No Details →
v0.0.0-20210730205404-4bbdd8ac624f 30 Jul 2021 U1 MIT No Details →
v3.2.2+incompatible 30 Jul 2021 U1 MIT No Details →
v3.2.2-0.20210730205404-4bbdd8ac624f+incompatible 30 Jul 2021 U1 MIT No Details →
v3.2.2-0.20210730202754-8e9d9ebf6f4a+incompatible 30 Jul 2021 U1 MIT No Details →
v3.2.2-0.20210729215709-324836737fe6+incompatible 29 Jul 2021 U1 MIT No Details →
v3.2.2-0.20210713063142-860640e8862d+incompatible 13 Jul 2021 U1 MIT No Details →
v3.2.2-0.20210622164956-3008b2bdeacb+incompatible 22 Jun 2021 U1 MIT No Details →
v0.0.0-20210608121815-5130b59fa758 08 Jun 2021 U1 MIT No Details →
v3.2.1+incompatible 08 Jun 2021 U1 MIT No Details →
v0.0.0-20210604144742-8a7d546baec2 04 Jun 2021 U1 MIT No Details →
v1.0.3-0.20210604144742-8a7d546baec2 04 Jun 2021 U1 MIT No Details →
v3.2.1-0.20210604144742-8a7d546baec2+incompatible 04 Jun 2021 U1 MIT No Details →
v0.0.0-20210529141834-26c069a8d756 29 May 2021 U1 MIT No Details →
v1.0.3-0.20210529141834-26c069a8d756 29 May 2021 U1 MIT No Details →
v0.0.0-20210529135444-590e8c64cd52 29 May 2021 U1 MIT No Details →
v0.0.0-20210529105905-08e48a8c90ac 29 May 2021 U1 MIT No Details →
v1.0.3-0.20210529105905-08e48a8c90ac 29 May 2021 U1 MIT No Details →
v0.0.0-20210529100528-c018921cb3d3 29 May 2021 U1 MIT No Details →
v0.0.0-20210529014511-0f726ea0e725 29 May 2021 U1 MIT No Details →
v1.0.3-0.20210529014511-0f726ea0e725 29 May 2021 U1 MIT No Details →
v0.0.0-20210529012641-6a07921e6808 29 May 2021 U1 MIT No Details →
v3.2.1-0.20200107013213-dc14462fd587+incompatible 07 Jan 2020 U1 MIT No Details →
v3.2.1-0.20200107012925-43aa750e43bc+incompatible 07 Jan 2020 U1 MIT No Details →
v3.2.1-0.20190726073049-e02edc50e49b+incompatible 26 Jul 2019 U1 MIT No Details →
v3.2.1-0.20190624232547-29384ebfa4ea+incompatible 24 Jun 2019 U1 MIT No Details →
v3.2.1-0.20190620180102-5e25c22bd5d6+incompatible 20 Jun 2019 U1 MIT No Details →
v3.2.1-0.20190516190944-5bff06a4f967+incompatible 16 May 2019 U1 MIT No Details →
v3.2.1-0.20190103155325-382e92cd0904+incompatible 03 Jan 2019 U1 MIT No Details →
v3.2.1-0.20181024141846-494b63caebf0+incompatible 24 Oct 2018 U1 MIT No Details →
v3.2.1-0.20180921172315-3af4c746e1c2+incompatible 21 Sep 2018 U1 MIT No Details →
v3.2.1-0.20180920003647-febd124631c4+incompatible 20 Sep 2018 U1 MIT No Details →
v3.2.1-0.20180718103447-a0d87832681f+incompatible 18 Jul 2018 U1 MIT No Details →
v0.0.0-20180308231308-06ea1031745c 08 Mar 2018 U1 MIT No Details →
v3.2.0+incompatible 08 Mar 2018 U1 MIT No Details →
v0.0.0-20171019215719-dbeaa9332f19 19 Oct 2017 U1 MIT No Details →
v3.1.0+incompatible 19 Oct 2017 U1 MIT No Details →
v3.0.1-0.20170703191307-08b573c69267+incompatible 03 Jul 2017 U1 MIT No Details →
v3.0.1-0.20170628071623-cb914dd542f2+incompatible 28 Jun 2017 U1 MIT No Details →
v0.0.0-20170608005149-a539ee1a749a 08 Jun 2017 U1 MIT No Details →
v3.0.1-0.20170608005149-a539ee1a749a+incompatible 08 Jun 2017 U1 MIT No Details →
v3.0.1-0.20170508165458-6c8dedd55f8a+incompatible 08 May 2017 U1 MIT No Details →
v3.0.1-0.20170316165535-fd360ca1aa50+incompatible 16 Mar 2017 U1 MIT No Details →
v3.0.1-0.20170201225849-2268707a8f08+incompatible 01 Feb 2017 U1 MIT No Details →
v3.0.1-0.20170131193656-53194fccb32b+incompatible 31 Jan 2017 U1 MIT No Details →
v0.0.0-20170104182250-a601269ab70c 04 Jan 2017 U1 MIT No Details →
v3.0.1-0.20170104182250-a601269ab70c+incompatible 04 Jan 2017 U1 MIT No Details →
v3.0.1-0.20161121095650-c5d6625a5076+incompatible 21 Nov 2016 U1 MIT No Details →
v3.0.1-0.20161101193935-9ed569b5d1ac+incompatible 01 Nov 2016 U1 MIT No Details →
v3.0.1-0.20160914142318-bf316c48137a+incompatible 14 Sep 2016 U1 MIT No Details →
v0.0.0-20160831183534-24c63f56522a 31 Aug 2016 U1 MIT No Details →
v3.0.1-0.20160831183534-24c63f56522a+incompatible 31 Aug 2016 U1 MIT No Details →
v3.0.1-0.20160827043244-7ff66c6bffa3+incompatible 27 Aug 2016 U1 MIT No Details →
v3.0.1-0.20160720160944-227c99f1afa2+incompatible 20 Jul 2016 U1 MIT No Details →
v0.0.0-20160705203006-01aeca54ebda 05 Jul 2016 U1 MIT No Details →
v3.0.1-0.20160705203006-01aeca54ebda+incompatible 05 Jul 2016 U1 MIT No Details →
v0.0.0-20160616191607-d8c133f5585d 16 Jun 2016 U1 MIT No Details →
v0.0.0-20160616191556-d2709f9f1f31 16 Jun 2016 U1 MIT No Details →
v3.0.0+incompatible 16 Jun 2016 U1 MIT No Details →
v2.7.0+incompatible 16 Jun 2016 U1 MIT No Details →
v2.6.1-0.20160615174954-2ed748cd9c41+incompatible 15 Jun 2016 U1 MIT No Details →
v2.6.1-0.20160607012035-317b82a6816a+incompatible 07 Jun 2016 U1 MIT No Details →
v2.6.1-0.20160504172110-0ef1a002d306+incompatible 04 May 2016 U1 MIT No Details →
v2.6.0+incompatible 13 Apr 2016 U1 MIT No Details →
v2.5.1-0.20160331181933-4ec621a2d1a2+incompatible 31 Mar 2016 U1 MIT No Details →
v2.5.0+incompatible 31 Mar 2016 U1 MIT No Details →
v2.4.1-0.20160114220927-e0e3b433f52c+incompatible 14 Jan 2016 U1 MIT No Details →
v2.4.1-0.20151220082550-1f970af1f874+incompatible 20 Dec 2015 U1 MIT No Details →
v2.4.1-0.20151219225827-5d11392aac6e+incompatible 19 Dec 2015 U1 MIT No Details →
v2.4.0+incompatible 16 Nov 2015 U1 MIT No Details →
v2.3.1-0.20151113230312-d9df83c8271c+incompatible 13 Nov 2015 U1 MIT No Details →
v2.3.1-0.20151020205303-acc5a5f31e34+incompatible 20 Oct 2015 U1 MIT No Details →
v2.3.1-0.20151001181616-eeccfeb20d40+incompatible 01 Oct 2015 U1 MIT No Details →
v2.3.1-0.20150820085358-abf9b1b8220f+incompatible 20 Aug 2015 U1 MIT No Details →
v2.3.0+incompatible 16 Jul 2015 U1 MIT No Details →
v2.2.1-0.20141227191423-bfe701fdf5f9+incompatible 27 Dec 2014 U1 MIT No Details →
v0.0.0-20141103211122-47b263f02057 03 Nov 2014 U1 MIT No Details →
v2.2.0+incompatible 11 Oct 2014 U1 MIT No Details →
v2.1.1-0.20141007054114-e1571c8f043b+incompatible 07 Oct 2014 U1 MIT No Details →
v2.1.0+incompatible 30 Sep 2014 U1 MIT No Details →
v2.0.0+incompatible 26 Aug 2014 U1 MIT No Details →
v1.0.2 26 Aug 2014 U1 MIT No Details →
v1.0.1 05 Jul 2014 U1 MIT No Details →
v1.0.0 16 Jun 2014 U1 MIT No Details →
v0.0.0-20140516231817-dea87c4cd8fb 16 May 2014 U1 MIT No Details →
v0.0.0-20140307233521-ba4268888e83 07 Mar 2014 U1 MIT No Details →
v0.0.0-20140129180831-955b8ff55f00 29 Jan 2014 U1 MIT No Details →
v0.0.0-20121222073103-924b188e6588 22 Dec 2012 U1 MIT No Details →

All 88 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 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/golang-jwt/jwt

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-30204: Excessive Memory Allocation in github.com/golang-jwt/jwt Package N/A unrated No fix published 26 Mar 2025

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/golang-jwt/jwt

Is github.com/golang-jwt/jwt safe to use?

Vulert records 1 vulnerabilities for github.com/golang-jwt/jwt in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/golang-jwt/jwt's Vulert package health score?

Vulert scores github.com/golang-jwt/jwt 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/golang-jwt/jwt affected?

Yes. v3.2.2+incompatible, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/golang-jwt/jwt should I use?

v3.2.2+incompatible 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/golang-jwt/jwt have?

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

0 vulnerabilities were recorded for github.com/golang-jwt/jwt in the last 12 months, and the oldest entry in this database dates to 26 Mar 2025. 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/golang-jwt/jwt 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/golang-jwt/jwt for upcoming vulnerabilities?

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