CVE-2026-71888
HighCVSS 8.7Exploitation Probability (EPSS)
Low risk1th percentile - higher than 1% of all known CVEs
Summary
In Bouncy Castle for Java before 1.86, the streaming CMS AuthenticatedData parser accepted messages where digestAlgorithm and authAttrs disagreed about whether authenticated attributes were present. The parser chose based on digestAlgorithm alone, so it could verify the content MAC and then return attributes via getAuthAttrs() as though they had been authenticated, even though the MAC never covered them. This also affects LTS before 2.73.13 and FIPS releases (BC-FJA) before the corresponding bcpkix-fips and bcutil-fips versions.
Risk Assessment
An attacker able to modify messages in transit could insert an authenticated attribute (such as an RFC 2634 ESSSecurityLabel) into an otherwise valid message without holding the key-encryption key or content-MAC key. An application making authorization, routing, or labelling decisions from those attributes would act on attacker-chosen values.
Recommendation
Upgrade Bouncy Castle for Java to 1.86 or later, the LTS line to 2.73.13 or later, and FIPS releases to bcpkix-fips 1.0.13/2.0.13/2.1.13 and bcutil-fips 2.0.8/2.1.8 or later. Until patched, do not base security decisions solely on attributes returned by getAuthAttrs() from CMS AuthenticatedData messages.
Other vulnerabilities in Bouncy Castle for Java
See all- CVE-2026-97873Medium
In Bouncy Castle for Java before 1.86 (and LTS before 2.73.13), the legacy PBES1 and PKCS#12 PBE families used an unbounded iteration count from untrusted input, allowing a small input to dictate arbitrary work. The fix rejects negative or over-limit counts (default 10,000,000) via the org.bouncycastle.pbe.max_iteration_count property.
- CVE-2026-71890High
In Bouncy Castle for Java before 1.86, validation of an MLS (RFC 9420) external commit's proposal list failed to verify that the removed leaf actually belonged to the joiner. This missing check allowed any party holding the group's public GroupInfo to send a commit with a Remove proposal naming any member, causing that member to be evicted and their slot in the ratchet tree to be taken over. The fix requires the removed leaf's credential to match the joiner's own new leaf credential on both the sending and receiving side.
- CVE-2026-71887High
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 when that binding omitted a Key Flags subpacket. isSigningKey() inherited SIGN_DATA from the primary key via getKeyFlags() and getApplyingSubpacket(), while verifyEmbeddedPrimaryKeyBinding() read only the binding signature's own hashed subpackets and treated the subkey as non-signing, so the same subkey was both signing-capable and exempt from cross-certification.
- CVE-2026-18040Medium
In Bouncy Castle for Java before 1.86, the HQC implementation leaked secret-derived data through two side channels: GF(2^8) arithmetic used lookup tables indexed by field elements, and the fixed-weight support sampler stopped scanning on collision and stored positions at a secret index. An attacker observing cache behavior or decapsulation timing can recover information about the HQC private key.
- CVE-2026-18036High
A side-channel vulnerability exists in the NTRU implementation of Bouncy Castle for Java before version 1.86. The reduction of secret values using the % operator in three helper functions causes execution time to depend on the secret operand (division by a variable), potentially allowing an attacker to recover information about the NTRU private key through timing measurements.
- CVE-2026-17507High
In the MLS implementation (RFC 9420) of Bouncy Castle for Java before 1.86, the uint32 leaf_index is stored as a signed int, allowing a wire value with the top bit set to decode as a negative number. Incorrect comparison in GroupKeySet.SecretTree.hasLeaf and Group.validateRemove allows bypassing membership checks, potentially leading to a DoS attack via unbounded growth of the node list and JVM heap exhaustion.
- CVE-2023-33201Medium
Bouncy Castle for Java before version 1.74 is affected by an LDAP injection vulnerability. This vulnerability affects applications that use an LDAP CertStore from Bouncy Castle to validate X.509 certificates, where the certificate's Subject Name is inserted into an LDAP search filter without proper escaping.
Original NVD description (English source)
In Bouncy Castle for Java before 1.86, the streaming CMS AuthenticatedData parser accepted a message whose digestAlgorithm and authAttrs fields disagreed about whether authenticated attributes were present. RFC 5652 sec. 9.1 pairs the two, requiring that authAttrs be present whenever digestAlgorithm is, and sec. 9.2 makes the MAC cover the DER encoding of authAttrs when they are present and the eContent OCTET STRING directly when they are not. CMSAuthenticatedDataParser has to choose between those two in its constructor, before it can reach authAttrs, which comes later in the SEQUENCE, so it chose on digestAlgorithm alone: for a message with digestAlgorithm absent but authAttrs present it verified the content MAC and then returned the attributes through getAuthAttrs() as though they had been authenticated, when the MAC had never covered them. An attacker able to modify a message in transit could insert an authenticated attribute, such as an RFC 2634 ESSSecurityLabel, into an otherwise valid message while holding neither the key-encryption key nor the content-MAC key, and an application taking an authorization, routing or labelling decision from those attributes would act on attacker-chosen values. The content itself remained MAC-bound. asn1.cms.AuthenticatedData now rejects the mismatched pairing when parsing and CMSAuthenticatedDataParser cross-checks the two fields once authAttrs is read. This is a variant of CVE-2026-59642, which bound the content to the MAC for messages that legitimately carry authAttrs, and which does not address this case. This issue also affects Bouncy Castle for Java LTS before 2.73.13, and Bouncy Castle for Java FIPS (BC-FJA) before bcpkix-fips 1.0.13 (1.0.X series), 2.0.13 (2.0.X series) and 2.1.13 (2.1.X series), and bcutil-fips 2.0.8 (2.0.X series) and 2.1.8 (2.1.X series).
Vulnerability data from NVD (NIST) · CISA KEV · EPSS