<?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://db.gcve.eu</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, 07 May 2026 07:21:05 +0000</lastBuildDate>
    <item>
      <title>0fee73f7-2824-4188-91a3-32e24665448e</title>
      <link>https://db.gcve.eu/sighting/0fee73f7-2824-4188-91a3-32e24665448e/export</link>
      <description>{"uuid": "0fee73f7-2824-4188-91a3-32e24665448e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-M4MP-V249-X3MH", "type": "seen", "source": "https://t.me/arpsyndicate/498", "content": "#ExploitObserverAlert\n\nGHSA-m4mp-v249-x3mh\n\nDESCRIPTION: Exploit Observer has 85 entries related to GHSA-M4MP-V249-X3MH. When a HTTP/2 stream was reset (RST frame) by a client, there was a time window were the request's memory resources were not reclaimed immediately. Instead, de-allocation was deferred to connection close. A client could send new requests and resets, keeping the connection busy and open and causing the memory footprint to keep on growing. On connection close, all resources were reclaimed, but the process might run out of memory before that.\n\nGHSS: 5.9", "creation_timestamp": "2023-11-23T13:49:41.000000Z"}</description>
      <content:encoded>{"uuid": "0fee73f7-2824-4188-91a3-32e24665448e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-M4MP-V249-X3MH", "type": "seen", "source": "https://t.me/arpsyndicate/498", "content": "#ExploitObserverAlert\n\nGHSA-m4mp-v249-x3mh\n\nDESCRIPTION: Exploit Observer has 85 entries related to GHSA-M4MP-V249-X3MH. When a HTTP/2 stream was reset (RST frame) by a client, there was a time window were the request's memory resources were not reclaimed immediately. Instead, de-allocation was deferred to connection close. A client could send new requests and resets, keeping the connection busy and open and causing the memory footprint to keep on growing. On connection close, all resources were reclaimed, but the process might run out of memory before that.\n\nGHSS: 5.9", "creation_timestamp": "2023-11-23T13:49:41.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/0fee73f7-2824-4188-91a3-32e24665448e/export</guid>
      <pubDate>Thu, 23 Nov 2023 13:49:41 +0000</pubDate>
    </item>
  </channel>
</rss>
