CVE-2026-63571: Legion of the Bouncy Castle bc-csharp · Improper Verification of Cryptographic Signature
Affects Legion of the Bouncy Castle bc-csharpSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 2.7.0 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade bc-csharp and BouncyCastle.Cryptography to 2.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Legion of the Bouncy Castle Inc.bc-csharp | Affected
| Fixed in
|
NuGetBouncyCastle.Cryptographypkg:nuget/BouncyCastle.CryptographyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fixed version 2.7.0 of bc-csharp addresses this vulnerability. Users should upgrade to version 2.7.0 or later to ensure proper verification of attribute certificate signatures. Until upgraded, applications relying on these validators remain vulnerable. Patch status is not explicitly confirmed in the vendor advisory, but the affected versions are prior to 2.7.0, indicating the fix is included in 2.7.0.
Description
CVE-2026-63571 is a high-severity vulnerability in Legion of the Bouncy Castle Inc.'s bc-csharp library before version 2.7.0. It involves improper verification of cryptographic signatures in the attribute certificate path validator, allowing a remote attacker to forge X.509 attribute certificates. This flaw permits acceptance of forged certificates that name a trusted attribute authority as issuer but are not actually signed by it. Only applications using these specific classes for attribute certificate validation are affected.