CVE-2026-63571: Attribute certificate path validation does not verify the attribute certificate's signature

Severity: high (CVSS 7.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-10-02 · updated 2026-10-28
Weakness: CWE-347

Description

Improper verification of cryptographic signature in the attribute certificate path validator (PkixAttrCertPathValidator, also used by PkixAttrCertPathBuilder) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote attacker to have a forged X.509 attribute certificate accepted as valid, and so obtain whatever roles or privileges an application grants on the strength of its attributes, via an attribute certificate that names a trusted attribute authority as its issuer but was not signed by it, because the RFC 3281 validation steps check the holder and issuer certification paths, validity period, extensions and revocation status but never verify the attribute certificate's signature with the issuer's public key. Only applications that use these classes to validate attribute certificates are affected.

Affected products

Legion of the Bouncy Castle Inc. bc-csharp: before 2.7.0 — fixed in 2.7.0
Legion of the Bouncy Castle Inc. bc-csharp: before 2.7.0 — fixed in 2.7.0

How to fix

Upgrade to a fixed version: Legion of the Bouncy Castle Inc. bc-csharp 2.7.0; Legion of the Bouncy Castle Inc. bc-csharp 2.7.0. Check the vendor advisory for mitigations.

References

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