VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/robbert229/jwt is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 51 releases, from Apr 2021 to Dec 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/robbert229/jwt vulnerabilities

Vulert verdict on github.com/robbert229/jwt v2.0.0+incompatible i

Updated on 22 Oct 2026

Action needed: v2.0.0+incompatible 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 54/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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.0.0+incompatible — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 28 Dec 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 104 i
  • OpenSSF scorecard 1/10 i
  • Last release 103 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/robbert229/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
v0.0.0-20181108173914-5d9a261c51a5 08 Nov 2018 H1 U1 MIT Yes Details →
v1.0.1-0.20181108173914-5d9a261c51a5 08 Nov 2018 H1 U1 MIT Yes Details →
v2.0.1-0.20181108173914-5d9a261c51a5+incompatible 08 Nov 2018 H1 U1 MIT Yes Details →
v2.0.1-0.20181108171307-441b0fe4907b+incompatible 08 Nov 2018 H1 U1 MIT Yes Details →
v2.0.1-0.20181108171210-ed17e3773018+incompatible 08 Nov 2018 H1 U1 MIT Yes Details →
v2.0.1-0.20180809011946-2b6c09e38d06+incompatible 09 Aug 2018 H1 U1 MIT Yes Details →
v2.0.1-0.20180809004611-dea559d72bb0+incompatible 09 Aug 2018 H1 U1 MIT Yes Details →
v2.0.0+incompatible 07 Mar 2018 H1 U1 MIT Yes Details →
v1.0.1-0.20180222205813-2479b53da499 22 Feb 2018 H1 U1 MIT Yes Details →
v1.0.1-0.20180222201855-c702dd399b61 22 Feb 2018 H1 U1 MIT Yes Details →
v1.0.0 26 Oct 2017 H1 U1 MIT Yes Details →
v0.0.0-20171021070204-49f767f85495 21 Oct 2017 H1 U1 MIT Yes Details →
v0.0.0-20170503205759-859ddbc3c8fe 03 May 2017 H1 U1 MIT Yes Details →
v0.0.0-20170503164102-c9dd026909b2 03 May 2017 H1 U1 MIT Yes Details →
v0.0.0-20170426191122-ca1404ee6e83 26 Apr 2017 H1 U1 MIT Yes Details →
v0.0.0-20170419090522-eddce2404b81 19 Apr 2017 H1 U1 MIT Yes Details →
v0.0.0-20170303194658-2eb16e9a008d 03 Mar 2017 H1 U1 MIT Yes Details →
v0.0.0-20170303192404-4ae9a6d2228e 03 Mar 2017 H1 U1 MIT Yes Details →
v0.0.0-20170222045851-5481a4c110b8 22 Feb 2017 H1 U1 MIT Yes Details →
v0.0.0-20170222043400-952dbad157e7 22 Feb 2017 H1 U1 MIT Yes Details →
v0.0.0-20161004171053-90c019814ab1 04 Oct 2016 H1 U1 MIT Yes Details →
v0.0.0-20161004170911-5b939751c339 04 Oct 2016 H1 U1 MIT Yes Details →
v0.0.0-20160905155414-43f5069c6375 05 Sep 2016 H1 U1 MIT Yes Details →
v0.0.0-20160830025026-af53eb3ea84f 30 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160827063356-ea284071c8fa 27 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160827062937-8049f962d91c 27 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160827062720-406633e9ad80 27 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160827062259-8e60c2915e1a 27 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160827014546-a83d19f771b0 27 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160827014517-40c792ac2806 27 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160827004852-a1f7acdee334 27 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160827004517-7f4f381635d5 27 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160826200626-e883840a7703 26 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160815090402-54a832e3a660 15 Aug 2016 H1 U1 MIT Yes Details →
v0.0.0-20160615060453-9ddf3f1a4b98 15 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160615060428-12f0dd64659f 15 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160609170151-834fde29d4c7 09 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160609165030-9ea29c43635b 09 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160609164907-329e3bb6717f 09 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160609163520-3c5cd3deb76b 09 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160609163128-5d1c23cc2b4e 09 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160606071027-36c8519e09d7 06 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160606070913-487e36093744 06 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160606070615-407f96e2aa6f 06 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160606065824-3f376a97742c 06 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160606065501-73fe0e9e2037 06 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160606050409-4fda3b9b925e 06 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160605234442-f2e3145b57ee 05 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160605231130-0390d8d5f127 05 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160605225245-b15df59c1ea5 05 Jun 2016 H1 U1 MIT Yes Details →
v0.0.0-20160605220138-d47ee9381be9 05 Jun 2016 H1 U1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1

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

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-10004: Timing Side-Channel Vulnerability in robbert229/jwt 7.5 high 0.0.0-20170426191122-ca1404ee6e83 28 Dec 2022
CVE-2015-10004: Timing side-channel vulnerability in github.com/robbert229/jwt N/A unrated 0.0.0-20170426191122-ca1404ee6e83 14 Apr 2021

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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

Is github.com/robbert229/jwt safe to use?

Vulert records 2 vulnerabilities for github.com/robbert229/jwt 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/robbert229/jwt's Vulert package health score?

Vulert scores github.com/robbert229/jwt 54/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/robbert229/jwt affected?

Yes. v2.0.0+incompatible, 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/robbert229/jwt should I use?

v2.0.0+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/robbert229/jwt have?

2 vulnerabilities are recorded for github.com/robbert229/jwt 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/robbert229/jwt vulnerabilities disclosed?

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

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