CVE-2026-12185
Received Received - Intake

BKS/UBER Keystore Length Validation Flaw in Bouncy Castle

Publication date: 2026-08-03

Last updated on: 2026-08-03

Assigner: bcorg

Description
In Bouncy Castle for Java before 1.85, BKS/UBER keystore allocates from untrusted lengths before integrity check. This issue also affects Bouncy Castle for Java LTS before 2.73.12.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-03
Last Modified
2026-08-03
Generated
2026-08-03
AI Q&A
2026-08-03
EPSS Evaluated
N/A
NVD
CVE-2026-12185
EUVD
EUVD-2026-52021

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
bouncy_castle bouncy_castle to 1.85 (exc)
bouncy_castle bouncy_castle_lts to 2.73.12 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-789 The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Bouncy Castle for Java before 1.85 involves BKS/UBER keystores allocating memory based on untrusted length values before performing integrity checks. This could allow attackers to manipulate memory allocation by providing specially crafted keystore files.

Detection Guidance

This vulnerability affects Bouncy Castle keystore implementations in Java before versions 1.85 or LTS before 2.73.12. Detection requires checking the installed Bouncy Castle library version in your Java environment.

Impact Analysis

An attacker could exploit this to cause denial of service through memory exhaustion or potentially execute arbitrary code by crafting malicious keystore files. Systems using vulnerable versions of Bouncy Castle for Java may be at risk if they process untrusted keystores.

Compliance Impact

This vulnerability could impact compliance by potentially exposing sensitive data if keystores are compromised. Organizations handling regulated data (e.g., personal health information under HIPAA or personal data under GDPR) may face increased risk if they use vulnerable Bouncy Castle versions for encryption or authentication.

Mitigation Strategies

Update Bouncy Castle for Java to version 1.85 or later if using the main release, or to version 2.73.12 or later if using the LTS release. This addresses the untrusted length allocation issue in BKS/UBER keystores.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12185. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart