Skip to content

← Actionable
Medium, CVSS 4.3

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

CVE-2024-28180GHSA-c5q2-7r4c-mv6g

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Go github.com/go-jose/go-jose/v3

    Affected
    < 3.0.3
    Fixed in
    3.0.3
  • Go gopkg.in/square/go-jose.v2

    Affected
    <= 2.6.0
    Fixed in
    no fixed version recorded
  • Go github.com/go-jose/go-jose/v4

    Affected
    < 4.0.1
    Fixed in
    4.0.1
  • Go gopkg.in/go-jose/go-jose.v2

    Affected
    < 2.6.3
    Fixed in
    2.6.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS
  • CVE-2024-28180: 1.96% estimated exploitation activity in the next 30 days; percentile 80.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact An attacker could send a JWE containing compressed data that used large amounts of memory and CPU when decompressed by Decrypt or DecryptMulti. Those functions now return an error if the decompressed data would exceed 250kB or 10x the compressed size (whichever is larger). Thanks to Enze Wang@Alioth and Jianjun Chen@Zhongguancun Lab (@zer0yu and @chenjj) for reporting. Patches The problem is fixed in the following packages and versions: - github.com/go-jose/go-jose/v4 version 4.0.1 - github.com/go-jose/go-jose/v3 version 3.0.3 - gopkg.in/go-jose/go-jose.v2 version 2.6.3 The problem will not be fixed in the following package because the package is archived: - gopkg.in/square/go-jose.v2

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-c5q2-7r4c-mv6g

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-28180

Advisory: Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification)
IDs: CVE-2024-28180, GHSA-c5q2-7r4c-mv6g
Record: https://patchnext.com/advisories/cve-2024-28180 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/go-jose/go-jose/v3 3.0.3; github.com/go-jose/go-jose/v4 4.0.1; gopkg.in/go-jose/go-jose.v2 2.6.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/go-jose/go-jose/v3: affected < 3.0.3; fixed in 3.0.3
- Go gopkg.in/square/go-jose.v2: affected <= 2.6.0
- Go github.com/go-jose/go-jose/v4: affected < 4.0.1; fixed in 4.0.1
- Go gopkg.in/go-jose/go-jose.v2: affected < 2.6.3; fixed in 2.6.3

## Suggested inspection (read-only)
- Go github.com/go-jose/go-jose/v3: check the installed version with your package manager.
- Go gopkg.in/square/go-jose.v2: check the installed version with your package manager.
- Go github.com/go-jose/go-jose/v4: check the installed version with your package manager.
- Go gopkg.in/go-jose/go-jose.v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/go-jose/go-jose/v3, gopkg.in/square/go-jose.v2, github.com/go-jose/go-jose/v4, gopkg.in/go-jose/go-jose.v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c5q2-7r4c-mv6g (GitHub-reviewed advisory GHSA-c5q2-7r4c-mv6g lists affected ranges: Go github.com/go-jose/go-jose/v4 >=0 =0 =0 =0 <=2.6.0)

Commands are suggestions: review each one before running it.

Loading voting…