Skip to main content
VulnerabilityPublished Updated

CVE-2026-97873: Bouncycastle · In Bouncy Castle for Java before 1.86, the raw JCA provider's legacy PBES1 (PKCS#5 scheme 1) and PKCS#12 PBE families ran their password-based key

Affects bouncycastleSource GCVE Database

0
Compare
Authoritative record:CVE-2026-97873· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 1.86 : update bouncycastle when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.86, 2.73.13
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/U:Amber

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 16 Nov 2026.

What to do

Upgrade org.bouncycastle/bcprov-jdk15on to 1.86; org.bouncycastle/bcpkix-jdk15on to 2.73.13.

Affected software

ProductAffectedFixed in
Ubuntu Pro 16.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/xenialOther threatsAffected
  • =1.49+dfsg-3ubuntu1
  • =1.51-4ubuntu1
  • =1.51-4ubuntu1+esm1
Fixed in–
Ubuntu Pro 18.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/bionicOther threatsAffected
  • 1.57-1 – 1.59-1ubuntu0.1~esm1
4 affected builds
Fixed in–
Ubuntu Pro 20.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/focalOther threatsAffected
  • =1.61-1
  • =1.61-1ubuntu0.1~esm1
Fixed in–
Ubuntu Pro 22.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/jammyOther threatsAffected
  • 1.68-2 – 1.68-5ubuntu0.1~esm1
4 affected builds
Fixed in–
Ubuntu Pro 24.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/nobleOther threatsAffected
  • =1.72-2
  • =1.77-1
  • =1.77-1ubuntu0.1~esm1
Fixed in–
Ubuntu 26.10bouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=stonkingOther threatsAffected
  • =1.80-3
Fixed in–

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

AI-suggested

Users should upgrade to Bouncy Castle for Java version 1.86 or later, or LTS version 2.73.13 or later, where the iteration count parsing and bounding issues are fixed. The fix enforces limits on iteration counts and rejects invalid values, preventing excessive computational workload. No other mitigation is indicated.

Description

Bouncy Castle for Java versions before 1.86 and before 2.73.13 in the LTS branch contain a vulnerability in their legacy PBES1 (PKCS#5 scheme 1) and PKCS#12 password-based encryption (PBE) implementations. These implementations accept an iteration count for key derivation from untrusted input without proper bounds checking, allowing a small input to cause an arbitrary amount of computational work before verification. This can lead to denial-of-service conditions due to excessive CPU usage. The issue is addressed by bounding iteration counts under a configurable property and rejecting out-of-range values.

References

Community reviews

Loading reviews…