Bouncy Castle Java OOM via unbounded read before v1.85
CVE-2026-14682 Published on August 3, 2026
Possible OOM from unbounded up-front allocation on a definite-length read
In Bouncy Castle for Java before 1.85, Possible OOM from unbounded up-front allocation on a definite-length read. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series), and before bctls-fips 1.0.24.
Vulnerability Analysis
CVE-2026-14682 is exploitable with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity and availability.
Weakness Type
What is a Stack Exhaustion Vulnerability?
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.
CVE-2026-14682 has been classified to as a Stack Exhaustion vulnerability or weakness.
Products Associated with CVE-2026-14682
Want to know whenever a new CVE is published for Bouncycastle Bc Java? stack.watch will email you.
Affected Versions
Legion of the Bouncy Castle Inc. BC-JAVA:- Before 1.85 is affected.
- Version 2.73.0 and below 2.73.12 is affected.
- Version 1.0.0 and below 1.0.2.7 is affected.
- Version 2.0.0 and below 2.0.2 is affected.
- Version 2.1.0 and below 2.1.3 is affected.
- Version 1.0.0 and below 1.0.24 is affected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.