CVE-2026-71887

In Bouncy Castle for Java before 1.86, the high-level OpenPGP API accepted a data signature made by a signing subkey whose Subkey Binding signature carried no embedded Primary Key Binding (cross-certification) signature, in the case where that binding omits a Key Flags subpacket. RFC 9580 sec. 5.2.1.8 and sec. 10.1.3 require the embedded Primary Key Binding signature on any subkey that can issue signatures; it is the subkey's own statement that it belongs to the primary key it is bound under. OpenPGPCertificate resolved the subkey's key flags two different ways. isSigningKey() goes through getKeyFlags() and getApplyingSubpacket(), which falls back to the primary key's direct-key or primary User ID self-signature when the binding signature omits the subpacket, so the subkey inherited the primary's SIGN_DATA and counted as signing-capable; verifyEmbeddedPrimaryKeyBinding(), which enforces the requirement, reads the binding signature's own hashed subpackets, found no SIGN_DATA there, and returned early as a non-signing key without ever demanding the back signature. The same subkey was therefore signing-capable - so its signatures were attributed to the certificate and OpenPGPSignature.OpenPGPDocumentSignature.isValid() returned true - while being exempt from cross-certification, where GnuPG refuses the identical certificate and message. An attacker needs only the victim's public signing subkey, which is public material: they bind it to their own primary key with a Subkey Binding signature they are able to make, carrying no Key Flags and no embedded Primary Key Binding signature, which they cannot make without the subkey's private key, and a relying party verifying one of the victim's genuinely signed messages against that certificate is told the signature is valid and given the attacker's certificate as its issuer. Because a certificate's User IDs are self-asserted, a verifier that pins on the subkey's fingerprint or key ID while taking the identity from the enclosing certificate reports a real signature under an attacker-chosen identity. This is misattribution of a genuine signature rather than forgery of a new one: no private key is recovered, and the signature must be one the grafted subkey actually made. The low-level PGPSignature / PGPPublicKeyRing API performs no binding checks by design and is unaffected. Key Flags are a statement about the key the carrying signature refers to (RFC 9580 sec. 5.2.3.29), so a subkey no longer inherits them from the certificate-wide signatures of the primary key: a Subkey Binding signature that omits the subpacket now leaves the subkey with no capabilities rather than the primary's, which makes the flags the cross-certification check consults the same flags every other decision consults. Preferences and the other subpackets a direct-key signature carries are inherited as before, and the primary key itself, whose flags legitimately come from its own direct-key or User ID self-signature, is unaffected.

• CWE-345
• CWE-347

• https://github.com/bcgit/bc-java/commit/b51452fa48ccb578fc16b8222fce9eedf92c94d6
• https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9071887

Published

Oct 3, 2026

Last Modified

Oct 3, 2026

Status

Received

• Same Subject, Wrong User: A Cross-Issuer Account Takeover in n8nStrix found an identity-binding bug in n8n's token-exchange flow enabling account takeover.
• 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.

• CVE-2026-71879Missing authentication in initial setup functionality left e…9.1
• CVE-2026-7188Improper neutralization of special elements used in an SQL c…9.8
• CVE-2026-71880Interpretation of untrusted input in template engine in GBIF…7.6
• CVE-2026-71883In Bouncy Castle for Java LTS before 2.73.13, the one-shot n…8.2
• 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-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-71890In Bouncy Castle for Java before 1.86, validation of an MLS …8.7
• 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