Advisory record · GHSA-c5q2-7r4c-mv6g

Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification)

CVSS 4.3 MediumEPSS 0.020 · 80th percentile

Published by the GitHub Advisory Database at 7 Mar 2024, 22:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/go-jose/go-jose/v4Go<4.0.14.0.1
github.com/go-jose/go-jose/v3Go<3.0.33.0.3
gopkg.in/go-jose/go-jose.v2Go<2.6.32.6.3
gopkg.in/square/go-jose.v2Go<=2.6.0No fixed version yet
Identifiers
GHSA-c5q2-7r4c-mv6g · CVE-2024-28180 · GO-2024-2631
Weakness (CWE)
CWE-409
Published
7 Mar 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Go JOSE (github.com/go-jose/go-jose/v4 before 4.0.1, github.com/go-jose/go-jose/v3 before 3.0.3, and gopkg.in/go-jose/go-jose.v2 before 2.6.3) can be made to use large amounts of memory and CPU when decrypting a JWE with highly compressed data. An attacker who can send a crafted JWE to a Decrypt or DecryptMulti call can trigger this. Upgrade to 4.0.1, 3.0.3, or 2.6.3 to get the fix, which returns an error when decompressed data is too large. gopkg.in/square/go-jose.v2 (2.6.0 and earlier) has no fixed version listed because the package is archived.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.020, the 80th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.