Subject CN name-constraint check bypassed when non-DNS SAN present
wolfSSL
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wolfSSL wolfSSL |
| No fix yet |
Original description
A certificate with no dNSName SAN but another SAN type present (e.g. registeredID or iPAddress) bypassed the Subject CN dNSName name-constraint check. The CN-as-DNS fallback was gated on cert->subjectCN != NULL && cert->altNames == NULL && !cert->isCA instead of "no dNSName SAN", so an out-of-scope CN was accepted. This incomplete fix from CVE-2026-6731, leading to the name-constraint check issue, was introduced in wolfSSL version 5.9.2.
From the CVE record · wolfSSL