How severe is CVE-2024-28180?

CVE-2024-28180 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-28180?

CVE-2024-28180 affects the following packages: github.com/go-jose/go-jose/v4 (Go), github.com/go-jose/go-jose/v3 (Go), gopkg.in/go-jose/go-jose.v2 (Go), gopkg.in/square/go-jose.v2 (Go). Ecosystems affected: Go.

How do I fix CVE-2024-28180?

Update github.com/go-jose/go-jose/v4 to 4.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-28180 is resolved across your whole dependency graph.

How do I detect CVE-2024-28180 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/go-jose/go-jose/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-28180 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-28180 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-28180 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-28180?

CVE-2024-28180 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 80th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-28180?

CVE-2024-28180 is classified as CWE-409 (CWE-409). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-28180 published, and has it been updated?

CVE-2024-28180 was published on March 9, 2024 and was last updated on October 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2024-28180 — go-jose

MEDIUMFix: go-jose/go-jose@0dd4dd5

CVE-2024-28180 is a medium-severity (CVSS 4.3) CWE-409 vulnerability in github.com/go-jose/go-jose/v4. A fix is available for github.com/go-jose/go-jose/v4 — see the affected versions and patch details below.

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

Also known asGHSA-c5q2-7r4c-mv6gGO-2024-2631

Published

Mar 9, 2024

Updated

Oct 29, 2026

Affected

4 pkgs

Patched

3 / 4

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-28180.

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐹github.com/go-jose/go-jose/v4🐹github.com/go-jose/go-jose/v3🐹gopkg.in/go-jose/go-jose.v2🐹gopkg.in/square/go-jose.v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

4 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/go-jose/go-jose/v4`	all versions	4.0.1`go get github.com/go-jose/go-jose/v4@v4.0.1`
🐹Go	`github.com/go-jose/go-jose/v3`	all versions	3.0.3`go get github.com/go-jose/go-jose/v3@v3.0.3`
🐹Go	`gopkg.in/go-jose/go-jose.v2`	all versions	2.6.3`go get gopkg.in/go-jose/go-jose.v2@v2.6.3`
🐹Go	`gopkg.in/square/go-jose.v2`	all versions	No fix

Affected Products

2 products · 4 configurations

fedorafedoraproject

≥ 38 && ≤ 40

range

Application

go-josego-jose_project

≥ 4.0.0 && < 4.0.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/go-jose/go-jose/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/go-jose/go-jose/v4 to 4.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-28180 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2024-28180 (CC BY 4.0)

Product	Fixed in	Advisory
OADP-1.3-RHEL-9	`oadp/oadp-velero-plugin-rhel9:1.3.1-16`	RHSA-2024:1859
OpenShift Custom Metrics Autoscaler 2	`custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel8:2.12.1-376`	RHSA-2024:1812
OpenShift-Pipelines-1.15-RHEL-8	`openshift-pipelines-client-0:1.15.0-11496.el8`	RHEA-2024:4022
Red Hat Advanced Cluster Management for Kubernetes 2.12 for RHEL 9	`rhacm2/acm-cli-rhel9:v2.12.0-17`	RHSA-2024:8974
Red Hat Advanced Cluster Security 4.4	`advanced-cluster-security/rhacs-main-rhel8:4.4.0-17`	RHSA-2024:1570
Red Hat Ceph Storage 5.3	`rhceph/keepalived-rhel8:2.1.5-44`	RHBA-2025:1479
Red Hat Ceph Storage 7.1	`rhceph/ceph-nvmeof-cli-rhel9:1.2.19-1`	RHBA-2025:1772
Red Hat Enterprise Linux 8	`container-tools:rhel8-8100020240419145834.afee755d`	RHSA-2024:3254

Frequently Asked Questions

### 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 pr

O3 Security · Impact-Aware SCA

Is CVE-2024-28180 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works