Research / Finding
Disallow wildcard partial domains when using MatchDomainName.
F-WOLFSSL-NC-WILDCARD-001
Portfolio updated: 21 Oct 2026 (the last edit of this record set, not a re-check of every upstream source). Status, releases and attribution belong to each source below; none is inferred from another record.
Read the evidence · View in research browse
Recorded evidence
—score not recorded
Disallow wildcard partial domains when using MatchDomainName.
merged
details
- Finding IDs
- F-WOLFSSL-NC-WILDCARD-001
- Status
- merged
- Recorded credit
- PR body says: Thanks to Oleh Konko for the report.
- Note
- merged into master on 2026-03-19; merge commit 679366a5a49f. v5.9.1-stable release note also credits @1seal for the report. Scope: the change rejects partial wildcard patterns such as *foo.com in MatchDomainName (the character after the * must be a dot); it does not address all wildcard names.
F-WOLFSSL-NC-WILDCARD-001: Verification failures. Wildcard certificate names bypass name-constraint checks. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-WOLFSSL-NC-WILDCARD-001
Security area (1seal assessment): Identity. Wildcard certificate names bypass name-constraint checks. Reviewed 24 Sep 2026.
Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.
How this page groups evidence
This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.
Paper copy does not update. Current version: 1seal.org/research/findings/F-WOLFSSL-NC-WILDCARD-001/