CVE-2024-29371

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
15.5%
KEV
Not listed

Published

December 17, 2025

Last Modified

January 23, 2026

References (2)

Vendor Advisories for CVE-2024-29371(13)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjose4j2026-05-04redhat
redhatocp-tools-4/jenkins-rhel8:17767640962026-04-23redhat
redhatocp-tools-4/jenkins-rhel8:17767623472026-04-23redhat
redhatocp-tools-4/jenkins-rhel9:17769442152026-04-23redhat
redhatpatch2025-10-02redhat
redhateap8-yasson-0:3.0.3-3.redhat_00002.1.el9eap2024-08-15redhat
redhateap8-yasson-0:3.0.3-3.redhat_00002.1.el8eap2024-08-15redhat
redhatpatch2024-08-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.bitbucket.b_c:jose4j0.3.6 ... 0.9.5 (44 versions)0.9.6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:56 UTCEPSS rescore
  2. 2026-07-15 16:56 UTCEPSS rescore
  3. 2026-07-15 01:59 UTCEPSS rescore
  4. 2026-07-15 01:59 UTCEPSS rescore
  5. 2026-07-13 22:28 UTCEPSS rescore
  6. 2026-07-13 06:11 UTCEPSS rescore
  7. 2026-07-12 05:45 UTCEPSS rescore
  8. 2026-07-11 08:26 UTCEPSS rescore
  9. 2026-07-11 08:26 UTCEPSS rescore
  10. 2026-07-09 19:09 UTCEPSS rescore
  11. 2026-07-08 15:13 UTCEPSS rescore
  12. 2026-07-07 13:45 UTCEPSS rescore
  13. 2026-07-07 13:45 UTCEPSS rescore
  14. 2026-07-06 16:26 UTCEPSS rescore
  15. 2026-07-06 16:26 UTCEPSS rescore
  16. 2026-07-06 07:41 UTCOSV refresh
  17. 2026-07-06 02:22 UTCEPSS rescore
  18. 2026-07-06 02:22 UTCEPSS rescore
  19. 2026-07-05 02:29 UTCEPSS rescore
  20. 2026-07-04 06:30 UTCEPSS rescore
  21. 2026-07-02 17:00 UTCEPSS rescore
  22. 2026-07-01 15:05 UTCEPSS rescore
  23. 2026-06-30 23:21 UTCEPSS rescore
  24. 2026-06-30 23:21 UTCEPSS rescore
  25. 2026-06-29 14:05 UTCEPSS rescore
Show 62 more
  1. 2026-06-28 14:06 UTCEPSS rescore
  2. 2026-06-28 14:06 UTCEPSS rescore
  3. 2026-06-28 04:55 UTCEPSS rescore
  4. 2026-06-28 04:55 UTCEPSS rescore
  5. 2026-06-27 03:07 UTCEPSS rescore
  6. 2026-06-27 03:07 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 13:48 UTCEPSS rescore
  9. 2026-06-24 14:04 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-23 21:32 UTCEPSS rescore
  12. 2026-06-23 21:32 UTCEPSS rescore
  13. 2026-06-22 14:25 UTCEPSS rescore
  14. 2026-06-22 14:24 UTCEPSS rescore
  15. 2026-06-21 14:55 UTCEPSS rescore
  16. 2026-06-21 14:55 UTCEPSS rescore
  17. 2026-06-21 01:58 UTCEPSS rescore
  18. 2026-06-21 01:58 UTCEPSS rescore
  19. 2026-06-19 19:25 UTCEPSS rescore
  20. 2026-06-19 19:24 UTCEPSS rescore
  21. 2026-06-18 17:51 UTCEPSS rescore
  22. 2026-06-18 17:51 UTCEPSS rescore
  23. 2026-06-17 19:14 UTCOSV refresh
  24. 2026-06-17 17:52 UTCEPSS rescore
  25. 2026-06-17 17:52 UTCEPSS rescore
  26. 2026-06-16 17:52 UTCEPSS rescore
  27. 2026-06-16 17:51 UTCEPSS rescore
  28. 2026-06-15 17:47 UTCEPSS rescore
  29. 2026-06-14 23:16 UTCEPSS rescore
  30. 2026-06-13 22:59 UTCEPSS rescore
  31. 2026-06-13 22:59 UTCEPSS rescore
  32. 2026-06-12 23:11 UTCEPSS rescore
  33. 2026-06-12 23:11 UTCEPSS rescore
  34. 2026-06-11 13:59 UTCEPSS rescore
  35. 2026-06-10 22:17 UTCEPSS rescore
  36. 2026-06-10 13:21 UTCEPSS rescore
  37. 2026-06-10 13:21 UTCEPSS rescore
  38. 2026-06-08 14:16 UTCEPSS rescore
  39. 2026-06-07 15:24 UTCEPSS rescore
  40. 2026-06-07 15:24 UTCEPSS rescore
  41. 2026-06-06 13:46 UTCEPSS rescore
  42. 2026-06-06 13:46 UTCEPSS rescore
  43. 2026-06-05 22:46 UTCEPSS rescore
  44. 2026-06-05 22:46 UTCEPSS rescore
  45. 2026-06-05 06:09 UTCEPSS rescore
  46. 2026-06-05 06:09 UTCEPSS rescore
  47. 2026-06-04 13:11 UTCEPSS rescore
  48. 2026-06-04 13:11 UTCEPSS rescore
  49. 2026-06-04 13:11 UTCEPSS rescore
  50. 2026-06-02 20:12 UTCEPSS rescore
  51. 2026-06-02 20:12 UTCEPSS rescore
  52. 2026-06-01 13:51 UTCEPSS rescore
  53. 2026-06-01 13:51 UTCEPSS rescore
  54. 2026-06-01 13:51 UTCEPSS rescore
  55. 2026-05-31 22:30 UTCEPSS rescore
  56. 2026-05-31 22:30 UTCEPSS rescore
  57. 2026-05-31 00:15 UTCEPSS rescore
  58. 2026-05-31 00:15 UTCEPSS rescore
  59. 2026-05-29 17:27 UTCEG score recompute
  60. 2026-05-29 17:27 UTCVendor advisory
  61. 2026-05-29 13:43 UTCEPSS rescore
  62. 2026-05-29 13:43 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-29371?
CVE-2024-29371 is a high vulnerability published on December 17, 2025. 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…
When was CVE-2024-29371 disclosed?
CVE-2024-29371 was first published in the National Vulnerability Database on December 17, 2025, with the most recent update on January 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-29371 actively exploited?
CVE-2024-29371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-29371?
CVE-2024-29371 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-29371?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-29371, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-29371

Explore →

Is Your Infrastructure Affected by CVE-2024-29371?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs