6.9

CVE-2026-71892: legion of the bouncy castle inc. bc-fja Incorrect Comparison

CVSS: 6.9v4.0MediumAwaiting analysis
AliasesUBUNTU-CVE-2026-71892DEBIAN-CVE-2026-71892
Published 03-10-2026Last modified 05-10-2026

Vulnerability summary

CVE-2026-71892 is a medium (CVSS 6.9) Incorrect Comparison vulnerability in legion of the bouncy castle inc. bc-fja. EPSS estimates a 0.17% chance of exploitation in the next 30 days, higher than 6.3% of scored vulnerabilities.

Overall risk
28/100
0100
Medium · default modelHow is this calculated?
CVSS score
6.9/10
010
Medium · v4.0 (CVE.org)
EPSS score
0.17%
0%100%
Low · Change unavailable
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 1 · Related 1

Timeline

  1. 03-10-2026
    PublishedVulnerability first disclosed.
  2. 05-10-2026
    Last modifiedVulnerability information updated.

Description

In Bouncy Castle for Java before 1.86, the opt-in key-size validation on CMS key-transport recipients, org.bouncycastle.cms.jcajce.JceKeyTransRecipient.setKeySizeValidation(true), never ran for a message using RFC 9709 content-encryption key derivation (id-alg-cek-hkdf-sha256). The branch that should have selected the actual content-encryption algorithm carried in the key derivation AlgorithmIdentifier's parameters compared the encrypted-key byte array against the id-alg-cek-hkdf-sha256 object identifier, a comparison between a byte array and an ASN1ObjectIdentifier that is false for every possible input, so the check fell through to a key-size lookup on the outer wrapper OID. That OID identifies a key-derivation construction rather than a cipher and has no registered key size, so the size comparison was skipped entirely. A key-transport EnvelopedData or AuthEnvelopedData whose transported, HKDF-derived content-encryption key did not match the key size of the advertised content-encryption algorithm was therefore accepted even with validation explicitly enabled, silently defeating the only mechanism the API offers for enforcing recovered key size. The recipient now dispatches on the content-encryption AlgorithmIdentifier's algorithm OID, so validation checks the recovered key against the inner content-encryption algorithm. Messages with a matching key size, non-HKDF messages, and recipients that do not enable validation are unaffected. This issue also affects Bouncy Castle for Java FIPS (BC-FJA) before bcpkix-fips 2.0.13 (2.0.X series) and 2.1.13 (2.1.X series).

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.17%

Chance of exploitation in the next 30 days

Percentile

6%

Versus all other CVEs

30-day change

Change unavailable

Change unavailable

03-10-202619-10-2026
EPSS score
0.17%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Legion of the bouncy castle inc.2 products
  • bc-fja≥ 2.0.7, < 2.0.13 | ≥ 2.1.0, < 2.1.13
  • bc-java≥ 1.78, < 1.86
Debian1 product
  • bouncycastleAll versions (No fix recorded) | < 1.86-1
Ubuntu1 product
  • bouncycastleAll versions (No fix recorded)

3 vendors · 4 products

References

5 links