Answer in brief
CVE-2026-89133 records a Medium severity (CVSS 6.3) vulnerability in NameConstraints not enforced across unconstrained intermediate CA. The current sources do not mark it as known exploited. The current feed maps wolfSSL/wolfSSL (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps wolfSSL/wolfSSL (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| wolfSSL/wolfSSLgeneric | >=0 <=5.9.2 | Not reported |
Published upstream
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 27, 2026
wolfSSL versions 5.9.2 and earlier contain a flaw in the X.509 certificate validation logic where it fails to properly enforce NameConstraints extensions when there is an unconstrained CA tier between a name-constrained intermediate CA and the leaf certificate. wolfSSL incorrectly accepted certificates for hostnames they shouldn't be allowed to cover, due to a chain-walking state-machine bug that resets the validation state when encountering an intermediate without NameConstraints, thereby bypassing cryptographic delegation controls. This defect exists in the default build configuration that makes use of certificates where name constraint extensions are used. Thanks to Jack Lloyd, PathDiff, and Ben Smyth for reporting the issue.
Quoted source text, attributed separately from HOL analysis.