<?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://cve.radiocsirt.org</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, 17 Nov 2026 13:38:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-110353</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-110353</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HAProxy, HAProxy Enterprise Edition, HAProxy Kubernetes Ingress Controller, Haproxy Kubernetes Ingress Controller Enterprise&lt;/p&gt;
&lt;p&gt;HAProxy 3.2 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (worker-thread CPU exhaustion) via a truncated HTTP/2 PING frame. h2c_handle_ping in src/mux_h2.c does not check for a short read, unlike the other H2 frame handlers. Because the incomplete frame cannot be processed, its data is never consumed, and the H2 multiplexer tasklet is repeatedly woken by that pending data without making progress. The CPU spins until timeout http-request closes the connection, and an attacker opening many such connections can sustain high CPU usage.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HAProxy, HAProxy Enterprise Edition, HAProxy Kubernetes Ingress Controller, Haproxy Kubernetes Ingress Controller Enterprise&lt;/p&gt;
&lt;p&gt;HAProxy 3.2 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (worker-thread CPU exhaustion) via a truncated HTTP/2 PING frame. h2c_handle_ping in src/mux_h2.c does not check for a short read, unlike the other H2 frame handlers. Because the incomplete frame cannot be processed, its data is never consumed, and the H2 multiplexer tasklet is repeatedly woken by that pending data without making progress. The CPU spins until timeout http-request closes the connection, and an attacker opening many such connections can sustain high CPU usage.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-110353</guid>
    </item>
    <item>
      <title>USN-8972-1 — haproxy vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8972-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: haproxy, Ubuntu:24.04:LTS: haproxy, Ubuntu:26.10: haproxy, Ubuntu:26.04:LTS: haproxy&lt;/p&gt;
&lt;p&gt;It was discovered that HAProxy incorrectly handled truncated HTTP/2
PING frames. A remote attacker could possibly use this issue to cause
HAProxy to consume excessive CPU resources, leading to a denial of
service. (CVE-2026-110353)&lt;/p&gt;
&lt;p&gt;It was discovered that HAProxy incorrectly handled certain HTTP/1.1
chunked requests. A remote attacker could possibly use this issue to
cause HAProxy to consume excessive CPU resources, leading to a denial
of service. (CVE-2026-110354)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: haproxy, Ubuntu:24.04:LTS: haproxy, Ubuntu:26.10: haproxy, Ubuntu:26.04:LTS: haproxy&lt;/p&gt;
&lt;p&gt;It was discovered that HAProxy incorrectly handled truncated HTTP/2
PING frames. A remote attacker could possibly use this issue to cause
HAProxy to consume excessive CPU resources, leading to a denial of
service. (CVE-2026-110353)&lt;/p&gt;
&lt;p&gt;It was discovered that HAProxy incorrectly handled certain HTTP/1.1
chunked requests. A remote attacker could possibly use this issue to
cause HAProxy to consume excessive CPU resources, leading to a denial
of service. (CVE-2026-110354)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8972-1</guid>
    </item>
  </channel>
</rss>
