Jose4j is a Java library for handling JSON Web Tokens (JWT) and JOSE cryptographic operations, with a narrow but security-critical role in authentication and token validation across applications that depend on it. The recurring vulnerability signal centers on token-handling weaknesses including improper restriction of security token assignment, insufficient entropy in cryptographic operations, and uncontrolled resource consumption that can affect downstream applications relying on correct JWT processing. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Jose4j Project over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2024-29371HIGH 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 rat | Dec 17, 2025 | 7.5 | 27 | NO | NO |
CVE-2023-31582HIGH jose4j before v0.9.3 allows attackers to set a low iteration count of 1000 or less. | Oct 25, 2023 | 7.5 | 20 | NO | NO |
CVE-2023-51775MEDIUM The jose4j component before 0.9.4 for Java allows attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value. | Feb 29, 2024 | 6.5 | 17 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Jose4j Project.
Media articles that mention a CVE ID that affects a product developed by Jose4j Project — matched by CVE ID, not by vendor name.