VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/go-jose/go-jose/v4 is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 69 releases, from Mar 2024 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M2 U1
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 03 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

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

Vulert verdict on github.com/go-jose/go-jose/v4 v4.1.6 i

Updated on 23 Oct 2026

Action needed: v4.1.6 has 4 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 v4.1.6 — affected i
  • Vulnerabilities on record 4 over 2 years · 1 in the last year i
  • Latest disclosure 03 Apr 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 541 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 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/go-jose/go-jose/v4, 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.1.6 14 Oct 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.6-0.20261013171003-dd39a410ac24 13 Oct 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.6-0.20261008204415-13b7118f0127 08 Oct 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.6-0.20260903230540-25b55feb059b 03 Sep 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.5 03 Sep 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.5-0.20260903180652-b10771e937dd 03 Sep 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.5-0.20260819192550-e37f31a2de27 19 Aug 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.5-0.20260622192739-8d4e64dd6193 22 Jun 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.5-0.20260618233202-40ecb65e9717 18 Jun 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.5-0.20260617234048-928a820afdcb 17 Jun 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.5-0.20260609171533-2a98714fc355 09 Jun 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.5-0.20260609002740-85997a3fd6a8 09 Jun 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.5-0.20260402171449-d50302948f33 02 Apr 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.4 31 Mar 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.4-0.20260331233350-0e59876635f3 31 Mar 2026 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.4-0.20251124054120-ddffdbcec8bd 24 Nov 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.3 03 Oct 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.3-0.20250818145510-9860c65054c4 18 Aug 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.3-0.20250813210813-14239fdb15b8 13 Aug 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.2 18 Jul 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.2-0.20250718170453-a1565a41aa00 18 Jul 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.1 23 Jun 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.1-0.20250623234110-04339d94f057 23 Jun 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.1-0.20250530211300-e97691236832 30 May 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.1-0.20250424155630-c02d7be91934 24 Apr 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.1-0.20250421195336-4ff65aefe8a5 21 Apr 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.1-0.20250417163505-f777888c40de 17 Apr 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.1.0 07 Apr 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.6-0.20250310190305-0e4ab6846ac1 10 Mar 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.6-0.20250225203530-9dc538453357 25 Feb 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.6-0.20250225115440-783e3f5b2d4b 25 Feb 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.5 24 Feb 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.5-0.20250224200634-99b346cec4e8 24 Feb 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.4-0.20250131190418-22811e77bac0 31 Jan 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.5-0.20250131190418-22811e77bac0 31 Jan 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.5-0.20250114174106-9dde8493b25c 14 Jan 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.5-0.20250113145453-89172c5b51f2 13 Jan 2025 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.5-0.20241223151930-ee05e015574c 23 Dec 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.5-0.20241222195639-c0aef3ef5eaf 22 Dec 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.5-0.20240820182656-fdc2ceb0bbe2 20 Aug 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.5-0.20240730014032-10c69ef86e2b 30 Jul 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.4 27 Jul 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.4-0.20240727004637-15bc4c2ac457 27 Jul 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.3 09 Jul 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.3-0.20240708235131-2dcf8d06a293 08 Jul 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.3-0.20240618194316-ab072bd59d50 18 Jun 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.3-0.20240610212238-dc40081e51fa 10 Jun 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.3-0.20240516170508-696da50b9ef6 16 May 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.2 13 May 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.2-0.20240307210608-aabe78e07ec6 07 Mar 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.1 07 Mar 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20240307011304-5cc51763260e 07 Mar 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.1-0.20240307011304-5cc51763260e 07 Mar 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0 26 Feb 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20240226223237-2658f467ede2 26 Feb 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20240226184937-9c6fb61414cd 26 Feb 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20240226165647-31202557b449 26 Feb 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20240224001605-9f884ea4632e 24 Feb 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20240223224041-d37a508ffe8a 23 Feb 2024 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231218222708-29a78c8791f7 18 Dec 2023 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231212230530-833bb274d109 12 Dec 2023 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231212194335-455da8c42fdf 12 Dec 2023 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231212180303-98a066491980 12 Dec 2023 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231212000328-c353bc892999 12 Dec 2023 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231211231508-efa6b4607b81 11 Dec 2023 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231203170227-399d07fcb17f 03 Dec 2023 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231130173719-c74720ddfdb4 30 Nov 2023 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231130013459-9b5800e95c2a 30 Nov 2023 H1 M2 U1 Apache-2.0 Yes Details →
v4.0.0-20231130013441-4aa0f69ce2f1 30 Nov 2023 H1 M2 U1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2025 1
  • 2026 1

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

03 Vulnerabilities

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

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-34986: Go JOSE JWE Decryption Panic Vulnerability 7.5 high 4.1.4 03 Apr 2026
DoS in go-jose Parsing 6.9 medium 4.0.5 24 Feb 2025
Improper Handling of Highly Compressed Data in Go JOSE 4.3 medium 4.0.1 07 Mar 2024
Decompression bomb vulnerability in go-jose N/A unrated 4.0.1 15 Mar 2024

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

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

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

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

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

How many vulnerabilities does github.com/go-jose/go-jose/v4 have?

4 vulnerabilities are recorded for github.com/go-jose/go-jose/v4 in the Go ecosystem: 0 critical, 1 high, 2 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/go-jose/go-jose/v4 vulnerabilities disclosed?

1 vulnerability was recorded for github.com/go-jose/go-jose/v4 in the last 12 months, and the oldest entry in this database dates to 07 Mar 2024. 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/v4 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/v4 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/v4 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.