Skip to main content
VulnerabilityPublished Updated

CVE-2023-51775: jose4j · Uncontrolled Resource Consumption

Affects jose4jSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.9.4 when convenient.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.9.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Dec 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade org.bitbucket.b_c/jose4j to 0.9.4.

Affected software

ProductAffectedFixed in
Mavenorg.bitbucket.b_c/jose4jpkg:maven/org.bitbucket.b_c/jose4jOther threatsAffected
  • <0.9.4
Fixed in
  • 0.9.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade the jose4j library to version 0.9.4 or later, where this vulnerability is addressed. If immediate upgrading is not feasible, organizations should implement input validation to restrict the p2c parameter to reasonable values, preventing excessively large iteration counts. Additionally, applying resource usage limits or timeouts on cryptographic operations can help mitigate CPU exhaustion risks. Monitoring application performance and CPU usage for anomalies can provide early detection of exploitation attempts. Network-level protections such as rate limiting and filtering suspicious requests targeting cryptographic endpoints can reduce exposure. Finally, ensure secure coding practices and regular dependency audits to identify and remediate vulnerable components promptly.

Description

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.

References

Community reviews

Loading reviews…