{"id":4744,"date":"2026-09-04T18:46:44","date_gmt":"2026-09-04T10:46:44","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-54876"},"modified":"2026-09-04T18:46:44","modified_gmt":"2026-09-04T10:46:44","slug":"cve-2026-54876","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-54876","title":{"rendered":"CVE-2026-54876 [HIGH] &#8211; Issue summary: A malicious TLS server can cause a memory leak in a TLS\nclient that has ena"},"content":{"rendered":"<p>Issue summary: A malicious TLS server can cause a memory leak in a TLS<br \/>\nclient that has enabled OCSP response checking by sending an OCSP<br \/>\nresponse that contains no single response entries.<\/p>\n<p>Impact summary: An attacker can leak an attacker-tunable amount of memory<br \/>\nper TLS handshake in a victim client application. A long-running client<br \/>\nthat repeatedly connects to a malicious server can have its memory<br \/>\nexhausted, resulting in a Denial of Service.<\/p>\n<p>CWE: CWE-401: Missing Release of Memory after Effective Lifetime<\/p>\n<p>Description: The affected function is called during X.509 certificate<br \/>\nchain verification when OCSP response checking is enabled<br \/>\nwith the X509_V_FLAG_OCSP_RESP_CHECK or X509_V_FLAG_OCSP_RESP_CHECK_ALL<br \/>\nverification flags, for example when a TLS client verifies an OCSP<br \/>\nresponse stapled into the TLS handshake by the server.<\/p>\n<p>When the received BasicOCSPResponse contains an empty SEQUENCE OF<br \/>\nSingleResponse, which is permitted on the wire and accepted by the<br \/>\nOpenSSL decoder, the OCSP_BASICRESP structure allocated by<br \/>\nOCSP_response_get1_basic() was not freed because an early return<br \/>\nbypassed the cleanup code at the end of the function.<\/p>\n<p>The amount of memory leaked per handshake can be amplified by the<br \/>\nattacker by padding the certs field of the BasicOCSPResponse with<br \/>\nbogus certificates, which are parsed and stored in the leaked<br \/>\nstructure before the empty response check triggers the early return.<br \/>\nA long-running TLS client that repeatedly connects to a malicious<br \/>\nserver can have its memory exhausted over time.<\/p>\n<p>OCSP response checking is not enabled by default. Only client<br \/>\napplications that explicitly enable the OCSP response check<br \/>\nverification flags are affected.<\/p>\n<p>FIPS impact: no<\/p>\n<p>The FIPS modules in 4.0 and 3.6 are not affected by this issue as the<br \/>\naffected code is outside the OpenSSL FIPS module boundary.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Issue summary: A malicious TLS server can cause a memory leak in a TLS<br \/>\nclient that has enabled OCSP response checking by sending an OCSP<br \/>\nresponse that contains no single response entries.<\/p>\n<p>Impact summ<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-4744","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/4744","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4744"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4744"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4744"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}