wolfSSL before 4.8.1 incorrectly skips OCSP verification in certain situations of irrelevant response data that contains the NoCheck extens…

published 2021-08-12 5y ago modified 2026-06-17 4mo ago also EUVD-2021-25039

cvss: 5.9; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits: 0; none known

wolfSSL before 4.8.1 incorrectly skips OCSP verification in certain situations of irrelevant response data that contains the NoCheck extension.

Patch / fix

fixed in 1 distros 1 links 1

wolfssl wolfssl 4.8.1

wolfssl Debian 13, Debian 12 5.0.0-1

debian advisories DEBIAN-CVE-2021-38597

github.com/wolfSSL/wolfssl@f93083b commit

Is CVE-2021-38597 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness

CWE-345 Insufficient Verification of Data Authenticity

References

github.com /wolfSSL/wolfssl/commit/f93083be72a3b3d956b52a7ec13f307a27b6e093
patch, third-party-advisory
wolfssl.com /docs/wolfssl-changelog/
release-notes, vendor-advisory

Sources

CVE List CVE-2021-38597
NVD CVE-2021-38597

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.