---
id: CVE-2026-94417
title: >-
  When an application enables both OCSP and CRL revocation checking on one
  WOLFSSL_CTX or certificate manager, wolfSSL skips the CRL check for any peer
  certificate that carries no Authority Information Access OCSP URL, and accepts
  a certif…
summary: >-
  When an application enables both OCSP and CRL revocation checking on one
  WOLFSSL_CTX or certificate manager, wolfSSL skips the CRL check for any peer
  certificate that carries no Authority Information Access OCSP URL, and accepts
  a certif…
severity: low
cvss: 2.3
cvssVector: 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'
cwe:
  - CWE-299
vendor: wolfSSL
product: wolfSSL
affected:
  - wolfSSL <= 5.9.2
published: '2026-09-27'
updated: '2026-09-27'
sourceUpdated: '2026-09-27T10:16:59.700'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-94417'
references:
  - url: 'https://github.com/wolfSSL/wolfssl/pull/11500'
    label: facts@wolfssl.com
tags:
  - nvd
  - cve.org
cvssSource: cna
ingestedAt: '2026-09-27T09:45:46.031Z'
---

## Overview

When an application enables both OCSP and CRL revocation checking on one WOLFSSL_CTX or certificate manager, wolfSSL skips the CRL check for any peer certificate that carries no Authority Information Access OCSP URL, and accepts a certificate the loaded CRL lists as revoked. The soft-fail policy for a missing responder collapses the OCSP result onto success before the code decides whether the CRL fallback is still needed, so "no responder exists" becomes indistinguishable from "the responder answered good". Affected builds define both HAVE_OCSP and HAVE_CRL: --enable-ocsp --enable-crl directly, and implicitly --enable-all, --enable-distro, --enable-curl, --enable-nginx, --enable-haproxy, --enable-stunnel, --enable-lighty, --enable-wpas, --enable-strongswan, --enable-mosquitto, --enable-jni, --enable-openvpn and --enable-krb. An application is affected only if it calls both wolfSSL_CTX_EnableOCSP() (or wolfSSL_EnableOCSP() / wolfSSL_CertManagerEnableOCSP()) and wolfSSL_CTX_EnableCRL() (or the equivalents) with a CRL loaded; an application that uses OCSP stapling alone through wolfSSL_CTX_EnableOCSPStapling() is not affected, because that sets up a separate OCSP instance. The defect sits in ProcessPeerCerts() and is reachable over TLS 1.0 through TLS 1.3 and DTLS, both on a client verifying a server certificate and on a server verifying a client certificate under mutual or post-handshake authentication. When the skipped check falls on a chain certificate rather than the leaf, the unchecked intermediate is promoted into the certificate manager and stays a trusted signer for every later connection on that context, so an affected long-running process needs its WOLFSSL_CTX torn down and not only its library replaced. All wolfSSL versions from 5.9.2 and earlier are affected; on versions 5.9.1 and 5.9.2 the WOLFSSL_OCSP_CHECKALL configuration fails closed with OCSP_NEED_URL, which leaves wolfSSL_CTX_EnableOCSP() without CHECKALL as the exposed configuration on 5.9.2.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.