# CVE-2026-89102: OCSP stapling v2 multi accepts non-CA chain certificates as issuers

> A wolfSSL client flaw allows attackers to forge certificates by bypassing CA validation in OCSP stapling v2, enabling man-in-the-middle attacks.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/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-105188, DEBIAN-CVE-2026-89102, GHSA-f972-pmrg-c63r, UBUNTU-CVE-2026-89102

## What is CVE-2026-89102?

CVE-2026-89102 is a high-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

In wolfSSL versions 5.7.2 through 5.9.2 there is a client-side implementation flaw in RFC 6961, multiple OCSP response stapling, which can lead to certificate forgery. When a wolfSSL client enables OCSP stapling with the HAVE_CERTIFICATE_STATUS_REQUEST_V2 feature and calls wolfSSL_UseOCSPStaplingV2(ssl, WOLFSSL_CSR2_OCSP_MULTI, options), the client accepts any certificate in the peer's chain as a certificate authority without verifying that the certificate is actually authorized to act as one. This means that an attacker who possesses any certificate that chains to a CA trusted by the client (along with its private key) can forge certificates for arbitrary identities that will be accepted as valid by the client. The end entity certificate of the server is stored in the persistent trust store, affecting subsequent connections that reuse the context even when OCSP multi usage is not employed. Found by internal wolfSSL testing.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Wolfssl Wolfssl.

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

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

## Is CVE-2026-89102 being exploited?

There is no known exploitation of CVE-2026-89102 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-89102 and fix it if it is affected.

What it is: CVE-2026-89102 is a high-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-89102 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-89102/ (Markdown: https://insights.sbomify.com/CVE-2026-89102/index.md)
```

## Sources

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

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