cve.bz

CVE-2026-71886 legion of the bouncy castle inc. bc-java: Improper Authorization

8.2 highEPSS 0.2%

High (8.2) in legion of the bouncy castle inc. bc-java. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In Bouncy Castle for Java before 1.86, the high-level OpenPGP certificate API accepted a third-party certification or trust delegation from any component key of the issuing certificate, without requiring that component to have been granted the authority to certify. OpenPGPCertificate.getCertificationBy() and getDelegationBy() resolve a third-party signature by matching its issuer key identifier against every key of the third-party certificate, then verify the issuing component's binding chain and the signature itself; nothing checked that the issuing component carried the RFC 9580 sec. 5.2.3.29 certification key flag (CERTIFY_OTHER) when the signature was created. A subkey bound only with SIGN_DATA - the online signing subkey of exactly the offline-primary arrangement those key flags exist to express - could therefore issue a positive User ID certification over an attacker-controlled identity, or a full-trust depth-one direct-key delegation of introducer trust, and the API returned it as a valid signature chain attributed to the third-party certificate. An application treating getCertificationBy(...).isValid() or getDelegationBy(...) as an identity or trusted-introducer decision would attribute the attacker's assertion to the offline primary key. The same held for a legacy RSA subkey bound only for encryption, whose algorithm is nonetheless able to sign. This does not forge the primary key's signature or recover any private key; it promotes an already-compromised restricted subkey to the primary key's identity-issuing authority, defeating the containment the key-flag separation provides. A third-party certification or delegation is now attributed to the issuing certificate only when the component key that made it is the primary key, or is a subkey holding CERTIFY_OTHER when the signature was created, so certification-capable subkeys continue to be accepted; primary keys are accepted whatever their key flags say, since a primary key is certification-capable by construction and certificates carrying no key flags subpacket at all are common. Third-party revocations are deliberately outside the rule, since declining to honour one would keep trust alive rather than withdraw it.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/U:Amber
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-285 Improper Authorization
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-71886 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71886?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71886?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71886 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • legion of the bouncy castle inc.:bc-java

Versions

From the CNA's record in the CVE List.

ProductAffected
Legion of the Bouncy Castle Inc. BC-JAVAfrom 1.81 before 1.86

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13bouncycastleno fix listedDEBIAN-CVE-2026-71886
Debian14bouncycastle1.86-1DEBIAN-CVE-2026-71886
Ubuntu26.04:LTS, 26.10, Pro:16.04:LTS and 4 morebouncycastleno fix listedUBUNTU-CVE-2026-71886
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morebouncycastle1.86-150200.3.41.1SUSE-SU-2026:4797-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0bouncycastle1.86-160000.1.1SUSE-SU-2026:24461-1
openSUSELeap 16.0bouncycastle1.86-160000.1.1openSUSE-SU-2026:22169-1
openSUSETumbleweedbouncycastle1.86-1.1openSUSE-SU-2026:12090-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in Bouncy Castle's OpenPGP certificate API. When processing third-party certifications or trust delegations, the API fails to verify whether an issuing subkey carries the required certification authority flag (CERTIFY_OTHER). An attacker possessing a compromised or restricted subkey—such as a signing-only or legacy RSA encryption subkey—can issue fraudulent identity certifications or direct-key delegations that applications treat as authorized by the primary key. This bypasses cryptographic key-usage constraints, leading to improper identity verification and integrity compromise.

Red Hat's mitigation

Explicitly inspect key flags on issuing subkeys before accepting third-party certifications, or reject delegations originating from non-primary keys. Where feasible, avoid relying on high-level OpenPGP certificate evaluation APIs for trust decisions until upgraded.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3bcpg-jdk18onFix deferred
Red Hat JBoss Enterprise Application Platform 7bcpg-jdk15onNot affected
Red Hat JBoss Enterprise Application Platform 7bcpg-jdk18onFix deferred
Red Hat JBoss Enterprise Application Platform 8bcpg-jdk18onFix deferred
Red Hat JBoss Enterprise Application Platform Expansion Packbcpg-jdk18onFix deferred
Red Hat Single Sign-On 7bcpg-jdk18onFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-71886.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-285 (16).

References

Check your stackJSON