Back

HIGH

CMS verifySignatures returns true for SignedData with zero signers

Published Aug 3, 2026

Description

In Bouncy Castle for Java before 1.85, CMS verifySignatures returns true for SignedData with zero signers. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bcpkix-fips 1.0.12 (1.0.X series), 2.0.12 (2.0.X series) and 2.1.12 (2.1.X series).

Affected products

Remediation

Red Hat statement

Bouncy Castle for Java is bundled as a cryptographic provider across numerous Red Hat products. The CMS verifySignatures method incorrectly returns true for SignedData containing zero signers, so unsigned content may be treated as validly signed — a cryptographic signature-verification bypass with a high integrity impact. This affects applications that rely on Bouncy Castle CMS to verify signatures.

Red Hat mitigation

Red Hat is not aware of a mitigation for this flaw other than updating the affected Bouncy Castle component to a fixed version (bc-java 1.85, LTS 2.73.12, or BC-FJA bcpkix-fips 1.0.12/2.0.12/2.1.12) once available for the affected product.

Weaknesses (1)

References (7)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner bcorg
Published Aug 3, 2026
Updated Aug 3, 2026
Reserved Jul 6, 2026
CISA Vulnrichment
Updated Aug 3, 2026
NVD
Status Analyzed
Modified Aug 28, 2026
Red Hat
Severity Important
Public date Aug 3, 2026