CVE-2026-71888

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

• CWE-354

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

Published

Oct 3, 2026

Last Modified

Oct 3, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• 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-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-71887In Bouncy Castle for Java before 1.86, the high-level OpenPG…8.2
• 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
• CVE-2026-71897An improper authorization check in Apache DolphinScheduler a…4.3