CVE-2024-29371: jose4j is vulnerable to DoS via compressed JWE content

CVE-2024-29371 · Severity: high · CVSS 7.5 · Published 2025-12-17

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.

Technologies: org.bitbucket.b_c:jose4j (Maven). Vendors: Maven.

Quick answers

Is CVE-2024-29371 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-29371 being exploited in the wild.
How severe is CVE-2024-29371?
High severity, with a CVSS score of 7.5, published 17 December 2025.
Which products and versions are affected?
org.bitbucket.b_c:jose4j (Maven) ECOSYSTEM:introduced=0,fixed=0.9.6.
Is there a fix for CVE-2024-29371?
Yes. org.bitbucket.b_c:jose4j (Maven): upgrade to 0.9.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-29371?
Check whether you run Jose4j Project Jose4j or org.bitbucket.b_c:jose4j (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.bitbucket.b_c:jose4j (Maven): upgrade to 0.9.6 or later
    # set org.bitbucket.b_c:jose4j to 0.9.6 in your pom.xml or build.gradle

Affected products

  • Jose4j Project Jose4j
  • org.bitbucket.b_c:jose4j (Maven) ECOSYSTEM:introduced=0,fixed=0.9.6

Identifiers

  • CVE-2024-29371
  • GHSA-3677-xxcr-wjqv

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.