CVE-2026-103604: Legion of the Bouncy Castle bc-csharp · Inefficient Algorithmic Complexity
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.3% chance of exploitation in 30 days – higher than 25% 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:N/VA:H/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
Upgrade to bc-csharp version 2.7.0 or later, where this inefficient algorithmic complexity issue is fixed. No other mitigation is indicated. Patch status is confirmed by the version boundary provided. There is no indication of temporary fixes or vendor advisories stating otherwise.
Description
Inefficient algorithmic complexity in X.509 distinguished name string conversion (X509Name.ToString and IetfUtilities.ValueToString) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote unauthenticated attacker to cause a denial of service through CPU exhaustion via a certificate, CRL, certification request or other structure whose name contains a long attribute value made up of characters that must be escaped, such as commas, or of leading or trailing spaces, because each escaping backslash was inserted into the buffer being scanned, so the work grew quadratically with the length of the value. Applications are exposed when they convert such a name to a string, for example to log or display it, or compare it with IetfUtilities.RdnAreEqual, as PKIX path validation does for directoryName name constraints.