Is CVE-2026-95208 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-95208 being exploited in the wild.

How severe is CVE-2026-95208?

High severity, with a CVSS score of 7.5, published 8 October 2026.

Which products and versions are affected?

Wolfssl 5.9.2, 5.9.3, 5.9.4, master.

Is there a fix for CVE-2026-95208?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-95208 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-95208?

Check whether you run Wolfssl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-95208: wolfSSL certificate validation bypass in ConfirmNameConstraints()

CVE-2026-95208 · Severity: high · CVSS 7.5 · Published 2026-10-08

wolfSSL is a widely used TLS library protecting billions of connected devices and applications. A flaw in its certificate name constraint checking causes legitimate certificates without Subject Alternative Name extensions to be incorrectly rejected, breaking TLS connections to valid servers in name-constrained environments like banks, governments, and enterprises. The issue requires no attacker action and affects clients connecting to legitimate servers under certain PKI configurations.

Technologies: Wolfssl. Vendors: Wolfssl.

Quick answers

Is CVE-2026-95208 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-95208 being exploited in the wild.
How severe is CVE-2026-95208?: High severity, with a CVSS score of 7.5, published 8 October 2026.
Which products and versions are affected?: Wolfssl 5.9.2, 5.9.3, 5.9.4, master.
Is there a fix for CVE-2026-95208?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-95208 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-95208?: Check whether you run Wolfssl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The ConfirmNameConstraints() function in wolfcrypt/src/asn.c incorrectly applies DNS name constraints to the Subject Common Name (CN) of certificates lacking a dNSName SAN extension, contrary to RFC 5280 which restricts name constraints to present name forms. When a certificate's CN falls outside a CA's permitted name subtree, the validation fails with error -198 even for legitimate certificates. The vulnerability requires no crafted input; any wolfSSL client validating chains under a dNSName-constrained PKI will reject compliant no-SAN certificates whose CN is outside the constraint.

Affected products

wolfSSL wolfSSL 5.9.2, 5.9.3, 5.9.4, master

Timeline

2026-10-08: disclosed
2026-04-14: other: Vulnerable code introduced in commit e7b7fddac (v5.9.2-stable)
2026-07-08: other: Vulnerability widened by PR #10837 (v5.9.4-stable)

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.