Medium 6.3Published Sep 27, 2026

CVE-2026-89134Subject CN name-constraint check bypassed when non-DNS SAN present

Updated under an hour ago (2026-10-19 09:30 UTC)

Does this affect you?

It affects wolfSSL. Add what you run to find out whether that includes you.

EPSS puts the chance of exploitation in the next 30 days at 0.16%, higher than 4% of scored CVEs.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for wolfSSL

Exploited in the last 30 days

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.

CVSS: 6.3 MEDIUM (v4.0, CNA)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
Weakness (CWE): CWE-295
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): 0.16% (percentile 4)
Assigned by: wolfSSL
NVD analysis: Analyzed
Record last updated: Sep 29, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

wolfSSL wolfSSL wolfssl:wolfssl (from the name)	5.9.2	CNA record
wolfssl wolfssl wolfssl:wolfssl	5.9.2	NVD

References

https://github.com/wolfSSL/wolfssl/pull/10837patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.