---
id: CVE-2026-71885
title: >-
  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
summary: >-
  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 car…
severity: critical
cvss: 9.2
cvssVector: '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:Amber'
cwe:
  - CWE-287
  - CWE-295
vendor: Legion of the Bouncy Castle Inc.
product: bcmls
affected:
  - bcmls < 1.86
published: '2026-10-03'
updated: '2026-10-03'
sourceUpdated: '2026-10-03T09:17:04.730'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-71885'
references:
  - url: >-
      https://github.com/bcgit/bc-java/commit/77632a57edf350a7b5751fca1a5052daffa8dab2
    label: 91579145-5d7b-4cc5-b925-a0262ff19630
  - url: 'https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9071885'
    label: 91579145-5d7b-4cc5-b925-a0262ff19630
tags:
  - nvd
  - cve.org
cvssSource: cna
ingestedAt: '2026-10-03T09:42:13.787Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.