<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 19:12:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-35188 — Double-free When Checking OCSP Stapled Response</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-35188</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: A malicious server can exploit TLS OCSP stapling by delivering
a crafted response through the status_request extension, triggering a
double-free in the client&amp;#39;s certificate verification path.&lt;/p&gt;
&lt;p&gt;Impact summary: Successful exploitation allows an attacker to corrupt heap
memory via a double-free, potentially leading to a Denial of Service or
possibly an attacker controlled code execution or other undefined behavior.&lt;/p&gt;
&lt;p&gt;If OCSP stapling is enabled and the TLS client connects to a malicious server,
a crafted OCSP stapled response can trigger a double free in the TLS client
when the stapled response is checked.&lt;/p&gt;
&lt;p&gt;The OCSP stapling is not enabled by default. Reliable code execution
through a double-free is technically complex and highly environment-dependent
but the Denial of Service impact is straightforward to achieve, warranting
Moderate severity.&lt;/p&gt;
&lt;p&gt;No FIPS modules are affected by this issue as the affected code is outside
the OpenSSL FIPS module boundary.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: A malicious server can exploit TLS OCSP stapling by delivering
a crafted response through the status_request extension, triggering a
double-free in the client&amp;#39;s certificate verification path.&lt;/p&gt;
&lt;p&gt;Impact summary: Successful exploitation allows an attacker to corrupt heap
memory via a double-free, potentially leading to a Denial of Service or
possibly an attacker controlled code execution or other undefined behavior.&lt;/p&gt;
&lt;p&gt;If OCSP stapling is enabled and the TLS client connects to a malicious server,
a crafted OCSP stapled response can trigger a double free in the TLS client
when the stapled response is checked.&lt;/p&gt;
&lt;p&gt;The OCSP stapling is not enabled by default. Reliable code execution
through a double-free is technically complex and highly environment-dependent
but the Denial of Service impact is straightforward to achieve, warranting
Moderate severity.&lt;/p&gt;
&lt;p&gt;No FIPS modules are affected by this issue as the affected code is outside
the OpenSSL FIPS module boundary.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-35188</guid>
    </item>
  </channel>
</rss>
