Improper Verification of Cryptographic Signature
Source GCVE Database
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
Since the vulnerability affects versions before 2.7.0, upgrading to version 2.7.0 or later (once confirmed) is recommended if available. In the absence of a confirmed patch, applications should avoid relying on the affected classes for attribute certificate validation or implement additional signature verification checks as a temporary mitigation. Monitor vendor advisories for official remediation guidance.
Description
A cryptographic signature verification flaw exists in the attribute certificate path validator of Legion of the Bouncy Castle Inc. bc-csharp before version 2.7.0. This flaw allows a remote attacker to present a forged X.509 attribute certificate that is accepted as valid because the signature on the attribute certificate is not verified against the issuer's public key. Applications using these specific classes for attribute certificate validation are vulnerable to privilege escalation via forged attribute certificates.