Is CVE-2026-12185 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-12185 being exploited in the wild.

How severe is CVE-2026-12185?

High severity, with a CVSS score of 8.6, published 3 August 2026.

Is there a fix for CVE-2026-12185?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-12185 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-12185?

Check whether you run Bouncy Castle for Java or Bouncycastle Bouncy Castle For Java Lts at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-12185: Bouncy Castle for Java BKS/UBER keystore memory allocation DoS

CVE-2026-12185 · Severity: high · CVSS 8.6 · Published 2026-08-03

Bouncy Castle for Java is a widely-used cryptographic library that handles digital certificates and keystores. A flaw in BKS/UBER keystore parsing allows an attacker to trigger excessive memory allocation by providing untrusted length values before the integrity of the keystore data is verified. An attacker can exploit this to cause denial of service by exhausting server memory or crashing applications that process malicious keystore files.

Technologies: Bouncy Castle for Java, Bouncycastle Bouncy Castle For Java Lts. Vendors: Bouncy Castle, Bouncycastle.

Quick answers

Is CVE-2026-12185 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-12185 being exploited in the wild.
How severe is CVE-2026-12185?: High severity, with a CVSS score of 8.6, published 3 August 2026.
Which products and versions are affected?: Bouncy Castle for Java before 1.85.
Is there a fix for CVE-2026-12185?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-12185 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-12185?: Check whether you run Bouncy Castle for Java or Bouncycastle Bouncy Castle For Java Lts at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in BKS and UBER keystore implementations where untrusted length values are used to allocate memory before an integrity check (likely HMAC or similar) is performed on the keystore data. This allows an attacker to craft a malicious keystore file with artificially large length fields, causing the parser to allocate excessive heap memory. The vulnerability affects Bouncy Castle for Java before 1.85 and Bouncy Castle for Java LTS before 2.73.12. No authentication or user interaction is required—any application deserializing or loading a BKS/UBER keystore from an attacker-controlled source is vulnerable. The fix involves validating the integrity of the keystore before performing memory allocation based on untrusted length values.

Affected products

Bouncy Castle Bouncy Castle for Java before 1.85
Bouncy Castle Bouncy Castle for Java LTS before 2.73.12

Timeline

2026-08-03: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.