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

> Attackers can bypass certificate validation in wolfSSL by planting an unverified CA, requiring specific OpenSSL compatibility macros and X509_verify_cert usage.

- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** AZL-105191, DEBIAN-CVE-2026-89135, GHSA-m732-8qwx-39wm, UBUNTU-CVE-2026-89135

## What is CVE-2026-89135?

CVE-2026-89135 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-89135?

It affects 1 product.


Products: Wolfssl Wolfssl.

## How do I fix CVE-2026-89135?

No fix has been published for CVE-2026-89135 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-89135 being exploited?

There is no known exploitation of CVE-2026-89135 in the wild and no public exploit code.

## Other vulnerabilities in Wolfssl Wolfssl

- [CVE-2024-5991](https://insights.sbomify.com/CVE-2024-5991/): Buffer overread in domain name matching (critical 10.0)
- [CVE-2021-37155](https://insights.sbomify.com/CVE-2021-37155/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-36177](https://insights.sbomify.com/CVE-2020-36177/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2896](https://insights.sbomify.com/CVE-2014-2896/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2897](https://insights.sbomify.com/CVE-2014-2897/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89135 and fix it if it is affected.

What it is: CVE-2026-89135 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89135 in the wild and no public exploit code.

Affected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89135/ (Markdown: https://insights.sbomify.com/CVE-2026-89135/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89135
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89135
- OSV: https://osv.dev/vulnerability/CVE-2026-89135

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89135/
Summaries are generated and may contain mistakes; the official description above is the record.