Skip to main content
Vulnerability Database/CVE-2026-89134

CVE-2026-89134: wolfSSL Certificate Auth Bypass Vulnerability

CVE-2026-89134 is an authentication bypass flaw in wolfSSL that allows certificates with non-dNSName SANs to bypass name-constraint checks. This post explains its technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-89134 Overview

CVE-2026-89134 is a certificate validation flaw in wolfSSL that allows attackers to bypass Subject Common Name (CN) dNSName name-constraint checks. The vulnerability occurs when a certificate presents a Subject Alternative Name (SAN) of a non-DNS type, such as registeredID or iPAddress, while omitting a dNSName SAN entry. Under these conditions, wolfSSL incorrectly accepts an out-of-scope CN that should have been rejected by the name-constraint logic. The issue is an incomplete fix for CVE-2026-6731 and was introduced in wolfSSL version 5.9.2. The weakness is classified under CWE-295: Improper Certificate Validation.

Critical Impact

An attacker holding a certificate issued under a name-constrained CA can present a CN outside the permitted DNS scope, defeating the name-constraint protection that trust hierarchies rely on.

Affected Products

  • wolfSSL version 5.9.2 (vulnerability introduced)
  • Later wolfSSL releases prior to the fix referenced in GitHub Pull Request #10837
  • Applications and devices embedding affected wolfSSL builds for TLS/X.509 validation

Discovery Timeline

  • 2026-09-27 - CVE-2026-89134 published to NVD
  • 2026-09-29 - Last updated in NVD database

Technical Details for CVE-2026-89134

Vulnerability Analysis

X.509 name constraints allow a certificate authority to restrict the DNS namespaces under which subordinate certificates are valid. wolfSSL applies these constraints to the Common Name as a fallback when a certificate presents no SAN entries. The fallback decision, however, is implemented incorrectly. Instead of checking that no dNSName SAN is present, the code checks that the entire SAN set is absent. A certificate that includes an iPAddress or registeredID SAN but no dNSName SAN therefore skips the CN-based name-constraint evaluation. The CN then passes validation even when it falls outside the permitted DNS tree.

Root Cause

The defective gate is expressed as cert->subjectCN != NULL && cert->altNames == NULL && !cert->isCA. This condition is only true when there are no SANs at all. The correct semantics require evaluating the CN whenever no dNSName SAN is present, regardless of other SAN types. Because the check never fires for certificates carrying non-DNS SANs, the name-constraint policy is silently skipped. This logic error is residual from the earlier remediation for CVE-2026-6731 and reintroduced the exposure in wolfSSL 5.9.2.

Attack Vector

Exploitation requires an attacker to obtain or craft a certificate signed under a name-constrained issuer trusted by the victim. The attacker includes a non-DNS SAN entry, such as an iPAddress or registeredID, and sets the Subject CN to a hostname outside the permitted name space. When the victim validates the certificate with vulnerable wolfSSL, the CN check is bypassed and the certificate is accepted. The attacker can then impersonate a server for TLS sessions or sign content whose identity the relying party trusts. The attack vector is network-based and requires no user interaction, though attack complexity is elevated by the need to control a certificate under a constrained CA.

No verified public exploit code is available. See wolfSSL Pull Request #10837 for the authoritative patch and technical discussion.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-89134

Indicators of Compromise

  • Successful TLS handshakes where the server certificate contains a Subject CN outside the issuing CA's permitted DNS name space
  • Server certificates presenting iPAddress or registeredID SANs with no dNSName SAN but a hostname-formatted CN
  • Repeated certificate validation successes against a wolfSSL-based client where other TLS stacks reject the same certificate

Detection Strategies

  • Inventory binaries and firmware for wolfSSL version strings at or above 5.9.2 and below the fixed release
  • Parse captured X.509 certificates and flag combinations of absent dNSName SAN, present non-DNS SAN, and CN containing a DNS label
  • Compare validation outcomes between wolfSSL endpoints and a reference TLS stack to surface divergence on name-constraint enforcement

Monitoring Recommendations

  • Log full server certificate chains at TLS termination points to enable retrospective analysis of SAN composition
  • Alert on new issuance events from internal CAs where name constraints are declared but subject CNs fall outside the permitted subtree
  • Monitor outbound TLS connections from embedded and IoT devices known to ship with wolfSSL for anomalous certificate structures

How to Mitigate CVE-2026-89134

Immediate Actions Required

  • Identify all deployments of wolfSSL 5.9.2 and later that have not applied the fix from Pull Request #10837
  • Upgrade affected systems to the wolfSSL release containing the corrected CN-as-DNS fallback logic
  • Audit internal certificate authorities to confirm that name constraints are declared and that no issued certificates rely on CN-only hostname identity

Patch Information

The fix is tracked in wolfSSL GitHub Pull Request #10837. The corrected logic evaluates the CN name-constraint fallback based on the absence of a dNSName SAN specifically, rather than the absence of all SAN entries. Administrators should rebuild and redeploy any statically linked applications that embed wolfSSL after upgrading.

Workarounds

  • Where upgrade is not immediately feasible, configure relying parties to require a dNSName SAN and reject certificates that supply only non-DNS SAN types
  • Reduce the trust surface by removing name-constrained intermediate CAs that are not strictly required for operations
  • Enforce certificate pinning for critical TLS endpoints served by wolfSSL-based clients to limit exposure to unexpected CNs
bash
# Example: rebuild wolfSSL from source after applying the fix
git clone https://github.com/wolfSSL/wolfssl.git
cd wolfssl
# check out a release that includes PR #10837
./autogen.sh
./configure --enable-certgen --enable-certext
make
sudo make install

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.