CVE-2026-63571 PUBLISHED

Attribute certificate path validation does not verify the attribute certificate's signature

Assigner: bcorg
Reserved: 16.07.2026 Published: 02.10.2026 Updated: 02.10.2026

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.

Metrics

CVSS Vector: 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
CVSS Score: 8.7

Product Status

Vendor Legion of the Bouncy Castle Inc.
Product bc-csharp
Versions Default: unaffected
  • affected from 0 to 2.7.0 (excl.)

Credits

  • Discovered by Claude, Anthropic's AI assistant, and triaged by the Anthropic security team in collaboration with Anthropic Research. finder

References

Problem Types

  • CWE-347 Improper Verification of Cryptographic Signature CWE

Impacts

  • Authorization bypass (forged attribute certificate accepted as valid)