CVE-2024-29371: In jose4j before 0.9.6, an attacker can cause a Denial-of-Service (DoS) condition by crafting a malicious JSON

Q: How do I fix CVE-2024-29371?

jose4j: upgrade to 0.9.5. Exact commands for each OS are on this page.

Q: Is CVE-2024-29371 being exploited?

CVE-2024-29371 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-29371 affect?

CVE-2024-29371 affects jose4j. Severity is high (CVSS 7.5). In jose4j before 0.9.6, an attacker can cause a Denial-of-Service (DoS) condition by crafting a malicious JSON Web Encryption (JWE) token with an exceptionally high compression ratio. When this token is processed by the server, it results i

Q: How urgent is CVE-2024-29371?

Priority 41/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2024-29371 is a high-severity flaw (CVSS 7.5) affecting jose4j. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In jose4j before 0.9.6, an attacker can cause a Denial-of-Service (DoS) condition by crafting a malicious JSON Web Encryption (JWE) token with an exceptionally high compression ratio. When this token is processed by the server, it results in significant memory allocation and processing time during decompression.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 83%)
CISA exploited list	No
Weakness	CWE-1259
Published	2025-12-17
Last modified	2026-10-27

Publisher (CNA): MITRE · Vendor: jose4j project

Last updated 2026-10-27 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-12-17 16:16 UTCPublished CVE record published
2026-10-27 18:10 UTCUpdated Record last modified

jose4j project jose4j UPGRADE

Affected: < 0.9.5

Fixed in: 0.9.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jose4j || rpm -q jose4j || jose4j --version

2. UPGRADE to 0.9.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jose4j

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jose4j

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-29371?

jose4j: upgrade to 0.9.5. Exact commands for each OS are on this page.

Is CVE-2024-29371 being exploited?

CVE-2024-29371 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-29371 affect?

CVE-2024-29371 affects jose4j. Severity is high (CVSS 7.5). In jose4j before 0.9.6, an attacker can cause a Denial-of-Service (DoS) condition by crafting a malicious JSON Web Encryption (JWE) token with an exceptionally high compression ratio. When this token is processed by the server, it results i

How urgent is CVE-2024-29371?

Priority 41/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs