VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/go-jose/go-jose/v3 is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 38 releases, from Nov 2023 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 26 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/go-jose/go-jose/v3 vulnerabilities

Vulert verdict on github.com/go-jose/go-jose/v3 v3.0.5 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • 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 v3.0.5 — affected i
  • Vulnerabilities on record 3 over 2 years · 1 in the last year i
  • Latest disclosure 26 May 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 541 i
  • OpenSSF scorecard 5/10 i
  • Last release 6 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/go-jose/go-jose/v3, 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
v3.0.5 31 Mar 2026 M1 U2 Apache-2.0 Yes Details →
v3.0.5-0.20260331235259-be2f6548701d 31 Mar 2026 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20250226195949-5253038e3b5f 26 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v3.0.4 26 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v3.0.4-0.20250226183829-047dc99758ca 26 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v3.0.4-0.20240618214840-0f017e9bc3fd 18 Jun 2024 M1 U2 Apache-2.0 Yes Details →
v3.0.3 07 Mar 2024 M1 U2 Apache-2.0 Yes Details →
v3.0.3-0.20240307011735-11bb4e72bf7e 07 Mar 2024 M1 U2 Apache-2.0 Yes Details →
v3.0.2 23 Feb 2024 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20231128225616-25bce79fd677 28 Nov 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20231128225616-25bce79fd677 28 Nov 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20231108003909-47edce0854d5 08 Nov 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1 08 Nov 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20231108003827-65351c27657d 08 Nov 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230907165853-260aa2669b7e 07 Sep 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20230720154752-66f2b1f58064 20 Jul 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230720154752-66f2b1f58064 20 Jul 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230629155528-60b5aa7aa7c4 29 Jun 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230629013535-7fd60d7fc9b5 29 Jun 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230629012746-f5e055d0dfb6 29 Jun 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20230523200428-6531eff48398 23 May 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230523200428-6531eff48398 23 May 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230330210536-d55fbf6b9db5 30 Mar 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230329011136-b9c63f8b3f42 29 Mar 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230228173304-878ec67363eb 28 Feb 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20230123180444-b5b8c96bd255 23 Jan 2023 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20221117193127-916db76e8214 17 Nov 2022 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20221117193127-916db76e8214 17 Nov 2022 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20220520230150-32586461b3c4 20 May 2022 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20210613005559-6f2534b08aeb 13 Jun 2021 M1 U2 Apache-2.0 Yes Details →
v3.0.0-rc.1.0.20210613005559-6f2534b08aeb 13 Jun 2021 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20210613005559-6f2534b08aeb 13 Jun 2021 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20210605212743-5b99f3e5082e 05 Jun 2021 M1 U2 Apache-2.0 Yes Details →
v3.0.1-0.20210605212743-5b99f3e5082e 05 Jun 2021 M1 U2 Apache-2.0 Yes Details →
v3.0.0 05 Jun 2021 M1 U2 Apache-2.0 Yes Details →
v3.0.0-rc.1 05 Jun 2021 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20210605211057-30f4a6a3fe85 05 Jun 2021 M1 U2 Apache-2.0 Yes Details →
v3.0.0-20201202045841-aead58737f04 02 Dec 2020 M1 U2 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/go-jose/go-jose/v3

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial-of-Service Vulnerability in go-jose/go-jose/v3 N/A unrated 3.0.1 21 Nov 2023
Denial-of-Service Vulnerability in go-jose Package N/A medium 3.0.1 21 Nov 2023
CVE-2026-34986: Go JOSE Package Experiences Panic in JWE Decryption N/A unrated 3.0.5 26 May 2026

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/go-jose/go-jose/v3

Is github.com/go-jose/go-jose/v3 safe to use?

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

Vulert scores github.com/go-jose/go-jose/v3 79/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/go-jose/go-jose/v3 affected?

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

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

v3.0.5 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/go-jose/go-jose/v3 have?

3 vulnerabilities are recorded for github.com/go-jose/go-jose/v3 in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 2 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/go-jose/go-jose/v3 vulnerabilities disclosed?

1 vulnerability was recorded for github.com/go-jose/go-jose/v3 in the last 12 months, and the oldest entry in this database dates to 21 Nov 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/go-jose/go-jose/v3 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/go-jose/go-jose/v3 for upcoming vulnerabilities?

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