Finding and attribution
BC-JAVA’s MLS implementation checked a LeafNode signature against its own signature key but did not verify that an attached X.509 certificate used the same key. In deployments accepting external commits without a separate credential-admission check, an attacker could use another party’s certificate to join under that identity, evict the victim, derive the group epoch, decrypt later messages and send messages as the victim. The issue applies to X.509 credentials; basic credentials are unaffected. The application remains responsible for certificate-chain and trust-anchor validation.
Product: BC-JAVA. AI system: AISLE AI-native discovery engine (specific model not identified). Team / organization: AISLE (self-attributed AI-engine discovery); Bouncy Castle CNA record.
CVE identifiers: CVE-2026-71885.
AI and human contribution (source account): The primary AISLE CVE-discoveries index explicitly scopes its listed cases as CVEs discovered by its AI-native engine and individually lists CVE-2026-71885. This is AISLE's self-attributed case-specific AI-engine claim. The available sources do not identify a model, establish autonomy or first-discovery priority, or define the human/tool work split.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The CNA record gives the public CVE publication date. The checked sources do not establish exploitation in the wild or zero-day status.
Remediation status: fix documented. CNA version statements: BC-JAVA: 0 < 1.86 affected. CNA references a patch: https://github.com/bcgit/bc-java/commit/77632a57edf350a7b5751fca1a5052daffa8dab2.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 3 Oct 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Critical · highest recorded score 9.2. Documented technical effects: authentication bypass, data disclosure, data modification.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-71885: CVSS 4.0 · 9.2 (Critical) ·
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. CVE Program CNA record · checked 17 Nov 2026.
CVE-2026-71885: authentication bypass, data disclosure, data modification.
Prerequisites / affected scope: Only deployments that admit external commits without an independent credential-admission check; attacker credential is X.509 and victim certificate acceptance enables impersonation, message decryption and messages accepted as victim..
Exploitation evidence: The CNA description establishes the stated effect under these conditions. The checked source does not report exploitation in the wild.. Impact source · checked 17 Nov 2026.
Documented fix: CNA version statements: BC-JAVA: 0 < 1.86 affected. CNA references a patch: https://github.com/bcgit/bc-java/commit/77632a57edf350a7b5751fca1a5052daffa8dab2.