CVE-2026-13505: Legion of the Bouncy Castle BC-FJA · Missing Release of Resource after Effective Lifetime
Affects Legion of the Bouncy Castle BC-FJASource CVE Database V5
Not known to be exploited · CVSS 8.7 High · fixed in 2.1.3 : patch Legion of the Bouncy Castle BC-FJA soon.
Data as of 6 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.1.3, 2.0.2, 1.0.2.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/U:AmberExploitation evidence
Disclosed: evidence found.
CVE published 8 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade Legion of the Bouncy Castle BC-FJA to 2.1.3, 2.0.2 or 1.0.2.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Legion of the Bouncy Castle Inc.BC-FJA | Affected
| Fixed in
|
| Legion of the Bouncy Castle Inc.BC-FJA | Affected
| Fixed in
|
| Legion of the Bouncy Castle Inc.BC-FJA | Affected
| Fixed in
|
Mavenorg.bouncycastle/bc-fipspkg:maven/org.bouncycastle/bc-fipsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor has addressed the issue in versions 1.0.2.7, 2.0.2, and 2.1.3 by replacing finalizer-based zeroisation with java.lang.ref.Cleaner-based disposal. Users should upgrade to these fixed versions when available. No other mitigation steps are specified.
Description
In 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), sensitive key material held by the AES and DESede engines, the SP 800-90A DRBGs, SymmetricSecretKey and the PBKD and scrypt parameter classes was zeroised on garbage collection by overriding Object.finalize. Finalization runs at an unspecified time and in an unspecified order and is serviced by a single finalizer thread, so where objects carrying a finalizer are allocated faster than that thread retires them the pending-finalization queue grows without bound: disposal falls arbitrarily far behind, which can contribute to an OutOfMemoryError under load, and the key material those objects hold stays resident in the heap for as long as they are queued, defeating the purpose of the zeroisation. The behaviour was not a problem on Java 8 or Java 11; it is later JVMs, on which finalization has been deprecated and progressively de-emphasised, where it becomes one. Disposal of these classes now runs from a java.lang.ref.Cleaner registered in the multi-release jdk1.9 overlay, so on Java 9 and later it no longer depends on the finalizer being scheduled. Bouncy Castle for Java (bcprov) and Bouncy Castle for Java LTS are not affected, as neither implements the finalizer-based zeroisation scheme.