Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-71890 Overview
CVE-2026-71890 is an authorization flaw [CWE-863] in Bouncy Castle for Java prior to version 1.86. The vulnerability resides in org.bouncycastle.mls.protocol.Group.validateExternalCachedProposals, the validator for Messaging Layer Security (MLS, RFC 9420) external commit proposal lists. The validator counts proposals by type and bounds the removed leaf index but never ties the removed leaf to the joiner's identity. Any party holding the group's public GroupInfo can therefore issue an external commit that removes an arbitrary member and takes over that member's slot in the ratchet tree.
Critical Impact
An external joiner can evict any group member and hijack their position in the MLS ratchet tree, breaking the integrity guarantees of secure group messaging.
Affected Products
- Bouncy Castle for Java versions prior to 1.86
- MLS (RFC 9420) protocol implementation in org.bouncycastle.mls
- Applications invoking Group.externalJoin or Group.handle outside the gRPC interop harness
Discovery Timeline
- 2026-10-03 - CVE-2026-71890 published to the National Vulnerability Database
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-71890
Vulnerability Analysis
MLS external commits allow a new participant to join a group using only the public GroupInfo structure. RFC 9420 section 12.2 permits at most one Remove proposal in an external commit, intended for a resync scenario where the joiner removes an old version of themselves. The specification requires that the LeafNode in the commit's path field satisfy the same credential criteria as an Update for the removed leaf, so that its credential presents identifiers acceptable for the removed participant.
In Bouncy Castle, the ordinary proposal-list validator's self-remove rule is deliberately skipped on the external commit path, because a resync legitimately removes a leaf the joiner owns. However, no equivalent credential check replaced it. The result is that validateExternalCachedProposals accepts a Remove proposal naming any LeafIndex in the tree, regardless of whether the joiner's new credential corresponds to the removed member.
Root Cause
The credential binding between the removed leaf and the joiner's new LeafNode was enforced only inside the gRPC interop harness. Direct callers of the public Group.externalJoin and Group.handle API were never protected. This is a classic authorization gap [CWE-863] where authentication of the joiner succeeds but authorization to act on another member's leaf is not evaluated.
Attack Vector
An attacker who obtains a group's GroupInfo, which is exactly the artifact distributed to prospective external joiners, crafts an external commit containing a single Remove proposal referencing a victim's LeafIndex. Every receiving member applies the commit, evicting the targeted participant and installing the attacker in that ratchet tree slot. The attack requires no prior membership, no credentials belonging to the victim, and no user interaction from existing members.
No verified proof-of-concept code is published. See the GitHub CVE-2026-71890 Wiki for protocol-level details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-71890
Indicators of Compromise
- Unexpected Remove proposals in MLS external commits where the removed leaf's credential differs from the joiner's new LeafNode credential.
- Group state transitions in which a long-standing member is evicted immediately after an external join event.
- Application logs from Bouncy Castle MLS implementations showing successful Group.handle calls processing external commits with embedded Remove proposals.
Detection Strategies
- Audit MLS group transcripts for external commits that carry a Remove proposal and compare the removed leaf's credential against the joiner's committed credential.
- Inventory Java dependencies for bcprov, bcpkix, and related Bouncy Castle MLS artifacts at versions below 1.86.
- Instrument application code to log every invocation of Group.externalJoin and Group.handle with the proposal list contents for post-hoc review.
Monitoring Recommendations
- Monitor software composition analysis (SCA) output for Bouncy Castle versions prior to 1.86 across build pipelines and runtime environments.
- Alert on anomalous membership churn in MLS-backed messaging services, particularly evictions correlated with external join events.
- Track outbound and inbound distribution of GroupInfo objects, since possession is sufficient to mount the attack.
How to Mitigate CVE-2026-71890
Immediate Actions Required
- Upgrade Bouncy Castle for Java to version 1.86 or later across all applications that use the MLS protocol module.
- Rebuild and redeploy any services that embed Bouncy Castle MLS, including those pulling the library transitively.
- Review existing MLS group states for suspicious membership changes that occurred prior to patching.
Patch Information
The fix is applied in commit 7e8bb10eb90baddf3f10b8679f627462b9522d24. After the patch, an external commit carrying a Remove proposal is accepted only when the removed leaf's credential is identical to the one in the joiner's own new LeafNode, enforced on both sending and receiving sides.
Workarounds
- Restrict distribution of GroupInfo structures to trusted joiners only, since any holder of GroupInfo can mount the attack on unpatched versions.
- If upgrading is not immediately possible, wrap calls to Group.externalJoin and Group.handle with application-level logic that verifies the credential of any removed leaf matches the joiner's new leaf credential.
- Disable the MLS external join flow entirely in deployments where it is not operationally required.
# Maven dependency update to the patched release
# pom.xml
# <dependency>
# <groupId>org.bouncycastle</groupId>
# <artifactId>bcprov-jdk18on</artifactId>
# <version>1.86</version>
# </dependency>
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk18on -DdepVersion=1.86 -DforceVersion=true
mvn clean install
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

