Vulnerabilities / CVE-2026-89134

critical

CVE-2026-89134

A certificate with no dNSName SAN but another SAN type present (e.g. r ...

Published Modified CWE 295
In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by NVD.

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.

Affected packages and fixed versions

SourcePackageFixed in
alpine 3.24wolfssl5.9.4-r0
alpine edgewolfssl5.9.4-r0
debian 11wolfsslno fix listed
debian 12wolfsslno fix listed
debian 13wolfsslno fix listed
echowolfsslno fix listed
rapidfort debian 12wolfssl0:5.9.2-1.1
rapidfort debian 13wolfssl0:5.9.2-1.1

References

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.