How severe is CVE-2015-0886?

No CVSS score has been assigned to CVE-2015-0886 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-0886?

CVE-2015-0886 affects the following packages: org.mindrot:jbcrypt (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-0886?

Update org.mindrot:jbcrypt to 0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0886 is resolved across your whole dependency graph.

How do I detect CVE-2015-0886 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.mindrot:jbcrypt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-0886 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2015-0886 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-0886 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-0886?

CVE-2015-0886 has an EPSS (Exploit Prediction Scoring System) score of 4.8%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-0886?

CVE-2015-0886 is classified as CWE-190 (CWE-190). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-0886 published, and has it been updated?

CVE-2015-0886 was published on February 28, 2015 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2015-0886 — jbcrypt

CVE-2015-0886 is a CWE-190 vulnerability in org.mindrot:jbcrypt. A fix is available for org.mindrot:jbcrypt — see the affected versions and patch details below.

Integer Overflow or Wraparound in JBCrypt

Also known asGHSA-9h6p-92jq-888x

Published

Feb 28, 2015

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.mindrot:jbcrypt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Integer overflow in the crypt_raw 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.mindrot:jbcrypt`	all versions	0.4`org.mindrot:jbcrypt:0.4`

Affected Products

2 products · 4 configurations

fedorafedoraproject

3 versions

202122

Application

jbcryptmindrot

< 0.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.mindrot:jbcrypt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.mindrot:jbcrypt to 0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0886 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-0886 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works