CVE-2026-71885: Bouncycastle · In Bouncy Castle for Java before 1.86, the Messaging Layer Security (MLS, RFC 9420) implementation did not bind an X.509 credential to a LeafNode's
Affects bouncycastleSource GCVE Database
Not known to be exploited · CVSS 9.2 Critical : upgrade to 1.86 as a priority.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.86
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/U:AmberExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu Pro 16.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/xenialOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/bionicOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/focalOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 24.04 LTSbouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=esm-apps/nobleOther threats | Affected
| Fixed in– |
Ubuntu 26.10bouncycastlepkg:deb/ubuntu/bouncycastle?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Bouncy Castle for Java version 1.86 or later, where the vulnerability is fixed by enforcing that the end-entity certificate's public key matches the LeafNode's signature_key. Ensure that deployments perform independent credential admission checks and validate certificate chains to trust anchors as required by RFC 9420 section 5.3.1. Deployments using only basic credentials are not affected and require no action.
Description
Bouncy Castle for Java versions before 1.86 contain a vulnerability in the Messaging Layer Security (MLS) implementation where an X.509 credential is not properly bound to a LeafNode's signature key. This allows an attacker to present another party's certificate as their credential while signing with an unrelated key, potentially impersonating that party. The vulnerability affects deployments that accept external commits without independent credential admission checks. The issue is fixed by requiring the end-entity certificate's public key to match the signature key as per RFC 9420 section 5.3. Deployments using only basic credentials are not affected.
References
- nvd.nist.gov/vuln/detail/CVE-2026-71885 (opens in a new tab)
- github.com/bcgit/bc-java/commit/77632a57edf350a7b5751fca1a5052daffa8dab2 (opens in a new tab)
- github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9071885 (opens in a new tab)
- ubuntu.com/security/CVE-2026-71885 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-71885 (opens in a new tab)