Medium 6.3Published Sep 27, 2026

CVE-2026-89135Failed X509_verify_cert leaves unverified CA in shared CertManager

Updated under an hour ago (2026-10-19 09:40 UTC)

Does this affect you?

It affects wolfSSL. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for wolfSSL

Exploited in the last 30 days

A failed X509_verify_cert call permanently plants an unverified attacker CA in the shared CertManager, bypassing certificate validation in every type-blind sibling consumer (native TLS, OCSP, CRL, direct CM verify). This affects version 5.8.4 through 5.9.2 of wolfSSL with the macros (OPENSSL_EXTRA && !NO_CERTS && !WOLFCRYPT_ONLY) defined or built with --enable-opensslextra and the application is specifically making calls to the X509_verify_cert function.

CVSS: 6.3 MEDIUM (v4.0, CNA)CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Weakness (CWE): CWE-295
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: wolfSSL
NVD analysis: Analyzed
Record last updated: Sep 29, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

wolfSSL wolfSSL wolfssl:wolfssl (from the name)	from 5.8.4 through 5.9.2	CNA record
wolfssl wolfssl wolfssl:wolfssl	from 5.8.4 through 5.9.2	NVD

References

https://github.com/wolfSSL/wolfssl/pull/11009patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.