CVE-2026-11999: X.509 trust-chain bypass via path-depth exhaustion in wolfSSL_X509_verify_cert()
X.509 trust-chain bypass (path-depth exhaustion) in the OpenSSL compatibility certificate verifier (wolfSSLX509verifycert()). This affects only builds with --enable-opensslextra whose application calls X509verifycert() with caller-supplied untrusted intermediates; for those users it is critical, otherwise the library is unaffected. Native wolfSSL TLS/DTLS usage is not impacted. X509verifycert() returned success based only on the last verified link rather than on reaching a trust anchor: when the supplied chain is deeper than the verifier's maximum path depth (default 100), path building runs out of depth while still walking untrusted intermediates and the chain is accepted even though it never reaches a configured trust anchor, allowing acceptance of an attacker-controlled certificate. The default TLS handshake (WOLFSSLVERIFYPEER) is not affected; only applications doing manual or deferred verification through this API are.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-11999?
CVE-2026-11999 has a high severity rating of 8.2 according to the CVSS scoring system.
How do I fix CVE-2026-11999?
To mitigate CVE-2026-11999, it is recommended to update wolfSSL to a version that does not include the --enable-opensslextra option.
What does CVE-2026-11999 exploit?
CVE-2026-11999 exploits a trust-chain bypass due to path-depth exhaustion in the wolfSSL_X509_verify_cert() function.
Who is affected by CVE-2026-11999?
CVE-2026-11999 specifically affects applications that use wolfSSL with the --enable-opensslextra option and supply untrusted intermediates to X509_verify_cert().
When was CVE-2026-11999 published?
CVE-2026-11999 was published on June 25, 2026.