BC-JAVA: Memory Allocation with Excessive Size Value
CVE-2026-12185 is a high-severity memory allocation with excessive size value vulnerability in BC-JAVA from Legion of the Bouncy Castle, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 1.85 as the first without the flaw, so updating BC-JAVA to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.29% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update BC-JAVA to 1.85 or a later version.
- Update BC-LTS-JAVA to 2.73.12 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Legion of the Bouncy Castle | BC-JAVA | before 1.85 | 1.85 |
| Legion of the Bouncy Castle | BC-LTS-JAVA | 2.73.0 up to, but not including, 2.73.12 | 2.73.12 |
| Bouncycastle | Bouncy Castle For Java LTS | 2.73.11 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.1 | High | CNA |
| CVSS 3.1 | 8.6 | High | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Memory Allocation with Excessive Size Value
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.
How developers prevent this class of flaw
- Perform adequate input validation against any value that influences the amount of memory that is allocated. Define an appropriate strategy for handling requests that exceed the limit, and consider supporting a configuration option so that the administrator can extend the amount of memory to be used if necessary.
- Run your program using system-provided resource limits for memory. This might still cause the program to crash or exit, but the impact to the rest of the system will be minimized.
More Memory Allocation with Excessive Size Value vulnerabilities (CWE-789)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Third-party and government advisories
- github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9012185Third Party Advisory
Other vulnerabilities in BC-JAVA
- 8.2 High severity
- 7.1 High severity
- 8.7 High severity
- 8.7 High severity
- 8.7 High severity
- 8.2 High severity
Recent Memory Allocation with Excessive Size Value vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.