Skip to main content
VulnerabilityPublished Updated

CVE-2026-71892: Legion of the Bouncy Castle BC-JAVA · Incorrect Comparison

Affects Legion of the Bouncy Castle BC-JAVASource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.86 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.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-05.

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 BC-JAVA and Legion of the Bouncy Castle Inc./bcpkix to 1.86; BC-FJA and Legion of the Bouncy Castle Inc./bcpkix-fips to 2.1.13 or 2.0.13.

Affected software

ProductAffectedFixed in
Legion of the Bouncy Castle Inc.BC-JAVAAffected
  • >=1.78 <1.86
Fixed in
  • 1.86
Legion of the Bouncy Castle Inc.BC-FJAAffected
  • >=2.1.0 <2.1.13
Fixed in
  • 2.1.13
Legion of the Bouncy Castle Inc.BC-FJAAffected
  • >=2.0.7 <2.0.13
Fixed in
  • 2.0.13
MavenLegion of the Bouncy Castle Inc./bcpkixpkg:maven/Legion of the Bouncy Castle Inc./bcpkixOther threatsAffected
  • >=1.78 <1.86
Fixed in
  • 1.86
MavenLegion of the Bouncy Castle Inc./bcpkix-fipspkg:maven/Legion of the Bouncy Castle Inc./bcpkix-fipsOther threatsAffected
  • >=2.0.7 <2.0.13
  • >=2.1.0 <2.1.13
Fixed in
  • 2.0.13
  • 2.1.13

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

AI-suggested

Upgrade affected Bouncy Castle Java libraries to versions 1.86 or later, 2.0.13 or later for the 2.0.X FIPS series, and 2.1.13 or later for the 2.1.X FIPS series where the issue is fixed. No other mitigation is required as the fix addresses the root cause by correcting the key-size validation logic.

Description

CVE-2026-71892 is a vulnerability in Bouncy Castle for Java before version 1.86 and certain FIPS versions where the key-size validation for CMS key-transport recipients using RFC 9709 content-encryption key derivation (id-alg-cek-hkdf-sha256) was bypassed. The validation logic incorrectly compared incompatible data types, causing the key size check to be skipped entirely for these messages. This allowed acceptance of keys with mismatched sizes despite validation being enabled. The issue affects BC-JAVA versions >=1.78 <1.86 and FIPS versions >=2.0.7 <2.0.13 and >=2.1.0 <2.1.13. The flaw is fixed in versions 1.86, 2.0.13, and 2.1.13.

References

Community reviews

Loading reviews…