Legion of the Bouncy Castle Inc. bc-csharp
Name constraints bypass via trailing dot in rfc822Name, dNSName and URI hosts
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.7.0
Fixed in 2.7.0
Mitigation
Upgrade bc-csharp to 2.7.0 or later.
References
- Vendor advisory github.com/bcgit/bc-csharp/wiki/CVE-2026-10360…
- Patch github.com/bcgit/bc-csharp/commit/f196a22bbf77…
- Patch github.com/bcgit/bc-csharp/commit/be276e057775…
1 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.