CVE-2026-103602: Legion of the Bouncy Castle bc-csharp · Improper Certificate Validation
Affects Legion of the Bouncy Castle bc-csharpSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 2.7.0 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% 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:P/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 15 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 fix is available in bc-csharp version 2.7.0. Users should upgrade to version 2.7.0 or later to remediate this vulnerability. No vendor advisory content is provided to indicate alternative mitigations or temporary fixes.
Description
Improper certificate validation in PkixNameConstraintValidator in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who controls, or can obtain certificates from, a name-constrained intermediate CA to have certificates accepted during PKIX certification path validation for email addresses, DNS names or URI hosts that lie within excluded subtrees applying to that CA, via an rfc822Name, dNSName or uniformResourceIdentifier name whose host ends with a dot, because names and constraints were compared without first removing the RFC 1034 root-label trailing dot, so a fully qualified host name did not match an excluded subtree for the same host written without the dot.
References
- github.com/bcgit/bc-csharp/wiki/CVE-2026-103602 (opens in a new tab)
- github.com/bcgit/bc-csharp/commit/f196a22bbf7765cc19b0c4f4645c74ea7ad35e09 (opens in a new tab)
- github.com/bcgit/bc-csharp/commit/be276e057775a6a674a62e9d9a2583b229978f73 (opens in a new tab)
- github.com/bcgit/bc-csharp/commit/75c3c576602886180ed92a63c89419e3bd63b392 (opens in a new tab)