CVE-2026-63577 PUBLISHED

Name Constraints bypass: directoryName constraint matched at any position in the DN instead of as a prefix

Assigner: bcorg
Reserved: 16.07.2026 Published: 02.10.2026 Updated: 02.10.2026

Improper certificate validation in the directoryName name-constraint check (PkixNameConstraintValidator.WithinDNSubtree) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who controls, or can have certificates issued by, a name-constrained intermediate CA to get certificates accepted by PKIX path validation whose subject distinguished name, or a directoryName subjectAltName, lies outside the CA's permitted subtrees, via a name that places other RDNs ahead of a copy of the permitted RDN sequence, because the check looks for the constraint's first RDN anywhere in the name and compares the remaining RDNs from that position, instead of requiring the constraint to be an initial prefix of the name as RFC 5280 sections 4.2.1.10 and 7.1 require.

Metrics

CVSS Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
CVSS Score: 8.2

Product Status

Vendor Legion of the Bouncy Castle Inc.
Product bc-csharp
Versions Default: unaffected
  • affected from 0 to 2.7.0 (excl.)

Credits

  • Discovered by Claude, Anthropic's AI assistant, and triaged by the Anthropic security team in collaboration with Anthropic Research. finder

References

Problem Types

  • CWE-295 Improper Certificate Validation CWE

Impacts

  • Integrity (X.509 directoryName name-constraint bypass: certificates outside a constrained CA's permitted DN subtree are accepted)