Skip to main content
VulnerabilityPublished Updated

CVE-2026-71892: Bouncycastle · In Bouncy Castle for Java before 1.86, the opt-in key-size validation on CMS key-transport recipients

Affects bouncycastleSource GCVE Database

0
Compare
Authoritative record:CVE-2026-71892· Medium 6.9

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

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.86, 2.1.13, 2.0.13
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/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 15 Nov 2026.

What to do

Upgrade org.bouncycastle/bcprov-jdk15on to 1.86; org.bouncycastle/bc-fips to 2.1.13 or 2.0.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

A fix is available in Bouncy Castle for Java version 1.86 and in Bouncy Castle for Java FIPS versions 2.0.13 and 2.1.13. Users should upgrade to these versions or later to ensure proper key-size validation is enforced. Until upgraded, recipients should be aware that enabling key-size validation does not protect against this issue for HKDF-derived keys. No other mitigation is indicated by the vendor advisory.

Description

Bouncy Castle for Java versions before 1.86 have a flaw in the opt-in key-size validation for CMS key-transport recipients when using RFC 9709 content-encryption key derivation (id-alg-cek-hkdf-sha256). The validation check fails due to an incorrect comparison between a byte array and an ASN1ObjectIdentifier, causing the key size check to be skipped. This allows acceptance of EnvelopedData or AuthEnvelopedData messages with mismatched key sizes despite validation being enabled. The issue also affects Bouncy Castle for Java FIPS versions before bcpkix-fips 2.0.13 and 2.1.13. Non-HKDF messages and recipients without validation enabled are not affected.

References

Community reviews

Loading reviews…