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

CVE-2026-95208: wolfSSL Certificate Validation DoS Vulnerability

CVE-2026-95208 is a denial of service vulnerability in wolfSSL that causes TLS clients to incorrectly reject valid certificates. This article covers the technical details, affected versions, impact, and mitigation strategies.

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-95208 Overview

CVE-2026-95208 is a denial of service vulnerability in the ConfirmNameConstraints() function located in wolfcrypt/src/asn.c of wolfSSL versions 5.9.1 and 5.9.2. An attacker can supply crafted Certificate Authority (CA) certificates that cause wolfSSL-based TLS clients to incorrectly reject valid peer certificates that lack a Subject Alternative Name (SAN) extension. The flaw is categorized under [CWE-295: Improper Certificate Validation] and disrupts TLS session establishment. Because the attack vector is network-based and requires no authentication or user interaction, any wolfSSL client processing attacker-influenced certificate chains is exposed.

Critical Impact

Attackers can prevent wolfSSL-based TLS clients from establishing trusted connections by injecting crafted CA certificates that cause legitimate certificates without SAN extensions to be rejected.

Affected Products

  • wolfSSL version 5.9.1
  • wolfSSL version 5.9.2
  • Applications and devices embedding affected wolfSSL releases as a TLS client library

Discovery Timeline

  • 2026-10-08 - CVE CVE-2026-95208 published to NVD
  • 2026-10-08 - Last updated in NVD database

Technical Details for CVE-2026-95208

Vulnerability Analysis

The vulnerability resides in ConfirmNameConstraints(), the routine wolfSSL uses to validate X.509 name constraints extensions carried on CA certificates. Name constraints allow a CA to limit the namespaces (DNS, email, IP, URI, directory names) for which subordinate certificates are considered valid. When wolfSSL evaluates a peer certificate against a CA that advertises name constraints, the function must handle the case where the peer certificate omits a Subject Alternative Name extension.

In wolfSSL 5.9.1 and 5.9.2, the constraint evaluation logic mishandles this scenario. A crafted CA certificate causes ConfirmNameConstraints() to reject otherwise valid leaf certificates that have no SAN, breaking certificate path validation. The result is a denial of service for TLS clients that cannot complete the handshake.

Root Cause

The root cause is improper certificate validation logic that fails to correctly reconcile name constraint rules with certificates lacking SAN extensions. The function treats the absence of SAN as a validation failure when evaluated against specifically shaped name constraints, instead of falling back to the certificate Subject field or accepting the constraint evaluation as inapplicable.

Attack Vector

An attacker positioned to influence the certificate chain presented to a wolfSSL client, including a malicious intermediate CA within a chain or a compromised upstream TLS endpoint, can supply a crafted CA certificate carrying hostile name constraint values. Legitimate downstream certificates without SAN are then refused by the client, preventing successful TLS session establishment and causing service disruption.

A proof-of-concept demonstrating the certificate shape and client behavior is published as a GitHub Gist Example. See the wolfSSL Official Site for vendor guidance.

Detection Methods for CVE-2026-95208

Indicators of Compromise

  • Repeated TLS handshake failures from wolfSSL clients citing certificate name constraint or SAN validation errors.
  • Unexpected certificate chains presenting CA certificates with unusual or restrictive nameConstraints extensions.
  • Sudden loss of connectivity to backend services from embedded or IoT devices using wolfSSL after a certificate chain update.

Detection Strategies

  • Inventory all deployments linking against wolfSSL and identify those running versions 5.9.1 or 5.9.2.
  • Inspect inbound and intermediate CA certificates for nameConstraints extensions and validate behavior against test leaf certificates lacking SAN.
  • Correlate TLS error telemetry with certificate chain changes to surface anomalous rejections.

Monitoring Recommendations

  • Alert on spikes in TLS handshake failure rates on services or clients that depend on wolfSSL.
  • Capture packet metadata or TLS error logs for certificate validation failures to accelerate triage.
  • Monitor software bill of materials (SBOM) output for presence of affected wolfSSL versions in firmware or container images.

How to Mitigate CVE-2026-95208

Immediate Actions Required

  • Identify all applications, firmware images, and appliances that bundle wolfSSL 5.9.1 or 5.9.2.
  • Upgrade affected deployments to a wolfSSL release that fixes ConfirmNameConstraints() once published by the vendor.
  • Restrict which CA certificates are trusted by wolfSSL clients to vetted roots to reduce exposure to attacker-controlled chains.

Patch Information

Monitor the wolfSSL Official Site for a fixed release addressing the ConfirmNameConstraints() handling of certificates without SAN. Rebuild and redistribute any downstream firmware or applications that statically link wolfSSL once an updated version is available.

Workarounds

  • Pin trusted CA certificates and avoid trusting third-party intermediates that advertise name constraints until patched.
  • Where feasible, ensure peer certificates issued within controlled PKI include a valid Subject Alternative Name extension.
  • Isolate wolfSSL-based clients behind trusted TLS terminators that validate certificates independently before relaying traffic.
bash
# Identify binaries linking an affected wolfSSL version on Linux hosts
for bin in $(find / -type f -executable 2>/dev/null); do
  strings "$bin" 2>/dev/null | grep -E "wolfSSL 5\.9\.(1|2)" \
    && echo "Affected: $bin"
done

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.