PatchSiren cyber security CVE debrief
CVE-2026-63576 Legion of the Bouncy Castle Inc. CVE debrief
A vulnerability in PkixNameConstraintValidator (ExtractHostFromURL) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a name-constrained subordinate CA to bypass permitted or excluded uniformResourceIdentifier name constraints during certification path validation. This vulnerability impacts certificate validation and certification path validation configurations, potentially allowing a bypass of name constraints. Defenders should assess exposure and prioritize verification and patching.
- Vendor
- Legion of the Bouncy Castle Inc.
- Product
- bc-csharp
- CVSS
- HIGH 8.2
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-02
- Original CVE updated
- 2026-10-28
- Advisory published
- 2026-10-02
- Advisory updated
- 2026-10-28
Who should care
Defenders responsible for certificate validation and certification path validation configurations should assess exposure and prioritize verification and patching. This includes operators of systems using bc-csharp, security teams, and vulnerability management teams. They should review the CVE record and NVD entry for additional information and verify the bc-csharp version.
Why it matters
Defenders should prioritize verifying the bc-csharp version and applying the patch to prevent potential bypass of name constraints during certification path validation.
- Potential bypass of name constraints during certification path validation
- Verification of bc-csharp version and patch application required
- Monitoring for potential bypass of name constraints necessary
Technical summary
The vulnerability is caused by improper certificate validation in PkixNameConstraintValidator (ExtractHostFromURL) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0. This allows a name-constrained subordinate CA to bypass permitted or excluded uniformResourceIdentifier name constraints during certification path validation. The vulnerability impacts certificate validation and certification path validation configurations. Defenders should prioritize verifying the bc-csharp version and applying the patch to prevent potential bypass of name constraints.
Defensive priority
Defenders should prioritize verifying the bc-csharp version and applying the patch to prevent potential bypass of name constraints.
Recommended defensive actions
- Verify bc-csharp version and apply patch if necessary
- Review certification path validation configurations
- Monitor for potential bypass of name constraints
- Perform vulnerability assessment
- Implement compensating controls
- Track exceptions and retest remediated assets
- Review source references for additional guidance
Evidence notes
The CVE record and NVD vulnerability detail provide information on the vulnerability. Patch references are available from the source references. The vulnerability has been described in the CVE record and NVD entry. The source references provide additional information on the patch. Defenders should verify the bc-csharp version and apply the patch if necessary.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-63576 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-63576
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-63576 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-63576
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/bcgit/bc-csharp/commit/f196a22bbf7765cc19b0c4f4645c74ea7ad35e09
91579145-5d7b-4cc5-b925-a0262ff19630 - Patch
-
Source reference
Unverified legacy reference
URL: https://github.com/bcgit/bc-csharp/wiki/CVE-2026-63576
91579145-5d7b-4cc5-b925-a0262ff19630 - Patch, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.