Finding and attribution
The PKIX attribute-certificate validator checked the issuer path and trust conditions but never verified the attribute certificate’s own signature. A submitted certificate could therefore name a trusted attribute authority, contain arbitrary attributes, and be accepted despite lacking that authority’s signature. The vendor scopes impact to applications using the attribute-certificate validation classes; ordinary certificate path validation and CMS/TLS/OCSP paths are not affected.
Product: Bouncy Castle C# PKIX attribute certificate validation. AI system: Claude (model snapshot unspecified). Team / organization: Anthropic.
CVE identifiers: CVE-2026-63571.
AI and human contribution (source account): The Bouncy Castle project advisory directly states that Claude, Anthropic’s AI assistant, discovered this vulnerability; it credits the Anthropic security team and Anthropic Research with triage. The record does not claim Claude independently validated or patched the issue.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The vendor wiki page is dated October 1, 2026. The cited sources establish public disclosure but do not establish exploitation in the wild or zero-day status.
Remediation status: fix documented. The vendor lists BC C# .NET 2.7.0 as fixed for versions 2.6.2 and earlier and the 2.7.0-beta.98 prerelease. BC C# .NET 2.7.0 fixes the validator; the vendor links the corresponding fix commit.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 1 Oct 2026. AI attribution dated 1 Oct 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 8.7. Documented technical effects: privilege escalation.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-63571: CVSS 4.0 · 8.7 (High) ·
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· Assessment scenarios: GENERAL. bcorg (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-63571: privilege escalation.
Prerequisites / affected scope: 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..
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: The vendor lists BC C# .NET 2.7.0 as fixed for versions 2.6.2 and earlier and the 2.7.0-beta.98 prerelease. BC C# .NET 2.7.0 fixes the validator; the vendor links the corresponding fix commit.