OCSP Response Checking · Client-Side Memory Leak
Affects MicrosoftSource GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 14 Nov 2026, 09:18 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopenssl/opensslpkg:github/openssl/opensslOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, monitoring and limiting OCSP response handling may reduce risk.
Description
A client-side memory leak vulnerability exists in the OCSP response checking functionality of Microsoft software versions 3.0 and 4.0. This issue relates to improper memory management during the handling of OCSP responses.