CVE-2026-89102CWE-295

CVE-2026-89102

Medium · published September 27, 2026

CVSS v3.1
6.5
EPSS
0%
Percentile
6.6
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
6.5 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CVSS v4.0
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
EPSS
0.00175 · 6.6th percentile
Weakness
CWE-295 · Improper Certificate Validation
Published
2026-09-27T14:16Z
Affected products (1)
ProductVersionsFixed in
wolfssl/wolfssl≥ 5.7.2, ≤ 5.9.2—
References (1)
EPSS history
Timeline
  • 28 SEP 03:29Z
    EPSS moved — → 0%
    epss
  • 27 SEP 09:22Z
    OCSP stapling v2 multi accepts non-CA chain certificates as issuers
    cvelistv5