<?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>Wed, 30 Sep 2026 18:13:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-7246 — HPACK table poisoning in gRPC C++, Python &amp; Ruby</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-7246</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Google gRPC&lt;/p&gt;
&lt;p&gt;It&amp;#39;s possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It&amp;#39;s also possible to use this vulnerability to leak other clients HTTP header keys, but not values.&lt;/p&gt;
&lt;p&gt;This occurs because the error status for a misencoded header is not cleared between header reads, resulting in subsequent (incrementally indexed) added headers in the first request being poisoned until cleared from the HPACK table.&lt;/p&gt;
&lt;p&gt;Please update to a fixed version of gRPC as soon as possible. This bug has been fixed in 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Google gRPC&lt;/p&gt;
&lt;p&gt;It&amp;#39;s possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It&amp;#39;s also possible to use this vulnerability to leak other clients HTTP header keys, but not values.&lt;/p&gt;
&lt;p&gt;This occurs because the error status for a misencoded header is not cleared between header reads, resulting in subsequent (incrementally indexed) added headers in the first request being poisoned until cleared from the HPACK table.&lt;/p&gt;
&lt;p&gt;Please update to a fixed version of gRPC as soon as possible. This bug has been fixed in 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-7246</guid>
    </item>
  </channel>
</rss>
