<?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://db.gcve.eu</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>Thu, 22 Oct 2026 20:24:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-110354</title>
      <link>https://db.gcve.eu/vuln/cve-2026-110354</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HAProxy, HAProxy Enterprise Edition, HAProxy Technologies HAProxy Kubernetes Ingress Controller, HAProxy Technologies Kubernetes Ingress Controller Enterprise&lt;/p&gt;
&lt;p&gt;HAProxy 3 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (persistent worker-thread CPU exhaustion) via an HTTP/1.1 chunked request. Although the H1 multiplexer drains the request before closing the stream, the parser repeatedly re-processes the same bytes without making progress. The affected thread stays busy at 100% CPU after timeouts expire and after the client disconnects, and repeated requests can consume all worker threads until the process is restarted.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HAProxy, HAProxy Enterprise Edition, HAProxy Technologies HAProxy Kubernetes Ingress Controller, HAProxy Technologies Kubernetes Ingress Controller Enterprise&lt;/p&gt;
&lt;p&gt;HAProxy 3 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (persistent worker-thread CPU exhaustion) via an HTTP/1.1 chunked request. Although the H1 multiplexer drains the request before closing the stream, the parser repeatedly re-processes the same bytes without making progress. The affected thread stays busy at 100% CPU after timeouts expire and after the client disconnects, and repeated requests can consume all worker threads until the process is restarted.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-110354</guid>
    </item>
  </channel>
</rss>
