CVE-2026-71888: CMS AuthenticatedData exposes attacker-inserted authAttrs when digestAlgorithm is absent

Severity: high (CVSS 8.7 v4.0)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-10-03 · updated 2026-10-06
Weakness: CWE-354

Description

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).

Affected products

Legion of the Bouncy Castle Inc. BC-FJA: from 1.0.0 before 1.0.13; from 2.0.0 before 2.0.13; from 2.1.0 before 2.1.13; from 2.0.0 before 2.0.8; from 2.1.0 before 2.1.8 — fixed in 1.0.13, 2.0.13, 2.0.8, 2.1.13, 2.1.8
Legion of the Bouncy Castle Inc. BC-JAVA: before 1.86; from 1.70 before 1.86 — fixed in 1.86
Legion of the Bouncy Castle Inc. BC-LTS-JAVA: from 2.73.0 before 2.73.13 — fixed in 2.73.13

How to fix

Upgrade to a fixed version: Legion of the Bouncy Castle Inc. BC-FJA 1.0.13, 2.0.13, 2.0.8, 2.1.13; Legion of the Bouncy Castle Inc. BC-JAVA 1.86; Legion of the Bouncy Castle Inc. BC-LTS-JAVA 2.73.13. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-71888 or the next vulnerability affects your stack