CVE-2026-89134
- Source
- https://cve.org/CVERecord?id=CVE-2026-89134
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89134.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-89134
- Downstream
- Published
- 2026-09-27T09:16:58Z
- Modified
- 2026-10-21T03:00:01Z
- Severity
-
- 6.3 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- Subject CN name-constraint check bypassed when non-DNS SAN present
- Details
-
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.
- Database specific
{ "cna_assigner": "wolfSSL", "cwe_ids": [ "CWE-295" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89134.json" }- References
Affected packages
Git / github.com/wolfssl/wolfssl
Affected ranges
- Type
- GIT
- Repo
- https://github.com/wolfssl/wolfssl
- Events
-
IntroducedLast Affected
- Database specific
-
Show details
{ "extracted_events": [ { "range": [ { "introduced": "5.9.2" }, { "last_affected": "5.9.2" } ], "source": "AFFECTED_FIELD", "strategy": "StandaloneSingleVersion" }, { "cpe": "cpe:2.3:a:wolfssl:wolfssl:5.9.2:*:*:*:*:*:*:*", "range": [ { "introduced": "5.9.2" }, { "last_affected": "5.9.2" } ], "source": "CPE_STRING" } ] }