# 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....

CVE-2026-71885 is fixed in bouncycastle on 1 platform, first by DEBIAN-CVE-2026-71885, released October 3, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-71885
- Priority: Routine
- CVSS: n/a
- EPSS: 0.0020
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Oct 3, 2026

## Description

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 signature_key. LeafNode.verify() checked a leaf's signature against the signature_key carried in the leaf itself, while the credential's X.509 certificate chain was stored but never parsed or validated, so the end-entity certificate's public key was never required to match signature_key as RFC 9420 sec. 5.3 requires. A party could therefore present another party's certificate as its credential while signing the leaf, and the enclosing KeyPackage, with an unrelated key, and be accepted under that other party's identity through KeyPackage.verify() and the Group leaf-validation path. In a deployment that admits external commits without an independent credential-admission check, an unauthenticated attacker could be admitted under a victim's X.509 identity, evict the victim (resynchronization compares whole credentials rather than signing keys), derive the current epoch, decrypt subsequent group messages, and send messages accepted as the victim. TreeKEM.LeafNode now requires the end-entity certificate's subject public key, in the cipher suite's signature encoding, to equal signature_key for an X.509 credential and rejects the leaf otherwise, including an empty chain or a certificate whose key type does not match the cipher suite; certificate-chain and identity validation to a trust anchor remain the application's responsibility per RFC 9420 sec. 5.3.1. Deployments using only basic credentials are unaffected.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | bouncycastle Debian 14 | 1.86-1 | [DEBIAN-CVE-2026-71885](https://patchblox.com/security/data/fix/linux/debian-cve-2026-71885.md) | Oct 3, 2026 |
| Linux | bouncycastle opensuse-leap 16.0 | 1.86-160000.1.1 | [OPENSUSE-SU-2026:22169-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22169-1.md) | Nov 7, 2026 |
| Linux | bouncycastle sles 15.6 | 1.86-150200.3.41.1 | [SUSE-SU-2026:4797-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4797-1.md) | Nov 7, 2026 |
| Linux | bouncycastle sles 15.7 | 1.86-150200.3.41.1 | [SUSE-SU-2026:4797-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4797-1.md) | Nov 7, 2026 |
| Linux | bouncycastle sles 16.0 | 1.86-160000.1.1 | [SUSE-SU-2026:24461-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24461-1.md) | Nov 7, 2026 |

---

Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.