CVE-2026-71890
Last modified
CVE-2026-71890 is a high-severity vulnerability rated 8.7/10 on the CVSS scale. In Bouncy Castle for Java before 1.86, validation of an MLS (RFC 9420) external commit's proposal list, org.bouncycastle.mls.protocol.Group.validateExternalCachedProposals, counted the proposals by type and bounded the removed leaf index but never established that the removed leaf had anything to do with the joiner. RFC 9420 sec.
Description
In Bouncy Castle for Java before 1.86, validation of an MLS (RFC 9420) external commit's proposal list, org.bouncycastle.mls.protocol.Group.validateExternalCachedProposals, counted the proposals by type and bounded the removed leaf index but never established that the removed leaf had anything to do with the joiner. RFC 9420 sec. 12.2 permits at most one Remove proposal in an external commit, with which the joiner removes an old version of themselves, and requires that where one is present the LeafNode in the commit's path field meet the criteria it would have to meet in an Update for the removed leaf, in particular that its credential present identifiers acceptable for the removed participant. The ordinary proposal-list validator's self-remove rule is deliberately not applied on this path, because a resync commit legitimately removes a leaf the joiner owns, but nothing was put in its place. Any party holding the group's public GroupInfo, which is precisely what an external joiner is meant to be given, could therefore commit a Remove naming any member's LeafIndex and have every member apply it, evicting that member and taking over their slot in the ratchet tree. The credential check that should have prevented this existed only in the gRPC interop harness and so protected no other caller of the public Group.externalJoin and Group.handle API. An external commit carrying a Remove is now accepted only when the removed leaf's credential is identical to the one in the joiner's own new leaf, on both the sending and the receiving side.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Legion of the Bouncy Castle Inc. | BC-JAVA | >= 1.73, < 1.86 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-71890?
How severe is CVE-2026-71890?
How do I fix CVE-2026-71890?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-71885In Bouncy Castle for Java before 1.86, the Messaging Layer S…9.2
- CVE-2026-71886In Bouncy Castle for Java before 1.86, the high-level OpenPG…8.2
- CVE-2026-71887In Bouncy Castle for Java before 1.86, the high-level OpenPG…8.2
- CVE-2026-71888In Bouncy Castle for Java before 1.86, the streaming CMS Aut…8.7
- CVE-2026-71889In Bouncy Castle for Java before 1.86, neither copy of PKIXC…8.7
- CVE-2026-7189Insertion of sensitive information into sent data vulnerabil…7.5
- CVE-2026-71891In Bouncy Castle for Java before 1.86, BLS12_381BasicScheme.…7.1
- CVE-2026-71892In Bouncy Castle for Java before 1.86, the opt-in key-size v…6.9
- CVE-2026-71897An improper authorization check in Apache DolphinScheduler a…4.3
- CVE-2026-71898An incorrect authorization check in Apache DolphinScheduler …4.3
- CVE-2026-71899A missing authorization vulnerability exists in the `query-d…6.5
- CVE-2026-71904Multiple DrayTek VigorAP models contain a command injection …7.2
Are you affected by CVE-2026-71890?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
