CVE-2026-71888

CMS AuthenticatedData exposes attacker-inserted authAttrs when digestAlgorithm is absent

  • High 8.7

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

Key facts

Published
3 Oct 2026
Last changed
5 Oct 2026
Assigned by
bcorg
EPSS
0.112% likely to be exploited in the next 30 days, higher than 1.41% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.7CVSS 4.0, Highfrom the CNA (bcorg)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/U:Amber

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Legion of the Bouncy Castle Inc.BC-JAVA
  • Default status: unaffected
  • 0 up to but excluding 1.86 (affected)
Legion of the Bouncy Castle Inc.BC-JAVA
  • Default status: unaffected
  • 1.70 up to but excluding 1.86 (affected)
Legion of the Bouncy Castle Inc.BC-LTS-JAVA
  • Default status: unaffected
  • 2.73.0 up to but excluding 2.73.13 (affected)
Legion of the Bouncy Castle Inc.BC-LTS-JAVA
  • Default status: unaffected
  • 2.73.0 up to but excluding 2.73.13 (affected)
Legion of the Bouncy Castle Inc.BC-FJA
  • Default status: unaffected
  • 1.0.0 up to but excluding 1.0.13 (affected)
  • 2.0.0 up to but excluding 2.0.13 (affected)
  • 2.1.0 up to but excluding 2.1.13 (affected)
Legion of the Bouncy Castle Inc.BC-FJA
  • Default status: unaffected
  • 2.0.0 up to but excluding 2.0.8 (affected)
  • 2.1.0 up to but excluding 2.1.8 (affected)

Timeline

  1. 3 Oct 2026 Published

Weakness

References