<?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 sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 11 Jun 2026 11:38:38 +0000</lastBuildDate>
    <item>
      <title>60e264c2-169c-4193-bb1f-5997824f9bf5</title>
      <link>https://vulnerability.circl.lu/sighting/60e264c2-169c-4193-bb1f-5997824f9bf5/export</link>
      <description>{"uuid": "60e264c2-169c-4193-bb1f-5997824f9bf5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7246", "type": "seen", "source": "https://t.me/cvedetector/2543", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-7246 - gRPC HTTP/2 Proxy HPACK Table Poisoning and Information Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-7246 \nPublished : Aug. 6, 2024, 11:16 a.m. | 36\u00a0minutes ago \nDescription : It'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's also possible to use this vulnerability to leak other clients HTTP header keys, but not values.  \n  \nThis 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.  \n  \nPlease 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. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-06T14:10:07.000000Z"}</description>
      <content:encoded>{"uuid": "60e264c2-169c-4193-bb1f-5997824f9bf5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7246", "type": "seen", "source": "https://t.me/cvedetector/2543", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-7246 - gRPC HTTP/2 Proxy HPACK Table Poisoning and Information Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-7246 \nPublished : Aug. 6, 2024, 11:16 a.m. | 36\u00a0minutes ago \nDescription : It'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's also possible to use this vulnerability to leak other clients HTTP header keys, but not values.  \n  \nThis 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.  \n  \nPlease 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. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-06T14:10:07.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/60e264c2-169c-4193-bb1f-5997824f9bf5/export</guid>
      <pubDate>Tue, 06 Aug 2024 14:10:07 +0000</pubDate>
    </item>
  </channel>
</rss>
