Quick answers
- Is CVE-2026-89135 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-89135 being exploited in the wild.
- How severe is CVE-2026-89135?
- Informational severity, published 27 September 2026.
- Which products and versions are affected?
- Wolfssl 5.8.4 through 5.9.2.
- Is there a fix for CVE-2026-89135?
- A patch was published on 2026-08-11. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-89135 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-89135?
- 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 vulnerability exists in wolfSSL's X509_verify_cert implementation when compiled with OpenSSL compatibility macros enabled. A failed certificate verification call stores an attacker-supplied CA in the shared CertManager without validation, and this poisoned state persists across all subsequent verification operations regardless of the consumer (TLS, OCSP, CRL, direct CM verify). The flaw affects versions 5.8.4 through 5.9.2 and requires the application to explicitly call X509_verify_cert with attacker-controlled input.
Affected products
- wolfSSL wolfSSL 5.8.4 through 5.9.2
Timeline
- 2026-09-27: disclosed
- 2026-08-11: patched