Integer Overflow or Wraparound in JBCrypt

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2015-0886: 4.80% estimated exploitation activity in the next 30 days; percentile 91.96 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Integer overflow in the cryptraw method in the key-stretching implementation in JBCrypt before 0.4 makes it easier for remote attackers to determine cleartext values of password hashes via a brute-force attack against hashes associated with the maximum exponent.

Published by the source

13 May 2022, 01:05 UTC

Last modified by the source

27 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 15:53 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9h6p-92jq-888x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2015-0886

Advisory: Integer Overflow or Wraparound in JBCrypt
IDs: CVE-2015-0886, GHSA-9h6p-92jq-888x
Record: https://patchnext.com/advisories/cve-2015-0886 (revision 1, source checked 26 Oct 2026, 15:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.mindrot:jbcrypt 0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.mindrot:jbcrypt: affected < 0.4; fixed in 0.4

## Suggested inspection (read-only)
- Maven org.mindrot:jbcrypt: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.mindrot:jbcrypt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9h6p-92jq-888x (GitHub-reviewed advisory GHSA-9h6p-92jq-888x lists affected ranges: Maven org.mindrot:jbcrypt >=0 <0.4)

Commands are suggestions: review each one before running it.