CVE-2026-89102

NameCVE-2026-89102
DescriptionIn 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.
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs1150338

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
wolfssl (PTS)bookworm5.5.4-2+deb12u2fixed
bookworm (security)5.5.4-2+deb12u3fixed
trixie5.7.2-0.1+deb13u2vulnerable
sid5.9.2-1.2fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
wolfsslsourcebookworm(not affected)
wolfsslsource(unstable)5.9.2-1.11150338

Notes

[trixie] - wolfssl <no-dsa> (Minor issue)
[bookworm] - wolfssl <not-affected> (no status_request_v2 pending-CA code in 5.5.4)
https://github.com/wolfSSL/wolfssl/pull/11027 (v5.9.4-stable)

Search for package or bug name: Reporting problems