Skip to main content
VulnerabilityPublished Updated

CVE-2026-13505: Bouncy Castle · Zeroisation of sensitive key material on garbage collection relies on finalization

Affects org.bouncycastle:bc-fipsSource GCVE Database

0
Authoritative record:CVE-2026-13505· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 1.0.2.7 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.2.7, 2.0.2, 2.1.3
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:Amber

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade org.bouncycastle:bc-fips to 1.0.2.7; org.bouncycastle:bc-fips to 2.0.2; org.bouncycastle:bc-fips to 2.1.3.

Affected software

ProductAffectedFixed in
Mavenorg.bouncycastle:bc-fipsAffected
  • <1.0.2.7
Fixed in
  • 1.0.2.7
Mavenorg.bouncycastle:bc-fipsAffected
  • >=2.0.0 <2.0.2
Fixed in
  • 2.0.2
Mavenorg.bouncycastle:bc-fipsAffected
  • >=2.1.0 <2.1.3
Fixed in
  • 2.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…