<?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 00:00:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-389871</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-389871</link>
      <description>EUVD-2026-389871</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-389871</guid>
    </item>
    <item>
      <title>fkie_cve-2026-105297</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-105297</link>
      <description>&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;Before version 0.8.1, Pingora&amp;#39;s HTTP/2 server used the h2 crate&amp;#39;s default limits unless the application set its own 16 MiB decoded header-list size and no limit on concurrent streams. A remote, unauthenticated client can send 1-byte HPACK references to a near-empty header, making the server allocate hundreds of thousands of header fields per stream across an unlimited number of streams on one connection, and use HTTP/2 flow control to keep those streams open. This can exhaust memory and degrade or terminate the Pingora process.&lt;/p&gt;
&lt;p&gt;Impact&lt;/p&gt;
&lt;p&gt;Remote, unauthenticated denial of service against any Pingora service that terminates HTTP/2 (h2 or h2c) without explicitly setting max_header_list_size and max_concurrent_streams. The reporter showed that a single connection could get a Pingora process with a 2 GiB memory limit OOM-killed.&lt;/p&gt;
&lt;p&gt;Note that Cloudflare CDN customers were unaffected, as internal Pingora services at Cloudflare do not have HTTP/2 clients.&lt;/p&gt;
&lt;p&gt;Mitigation:&lt;/p&gt;
&lt;p&gt;*&lt;/p&gt;
&lt;p&gt;Upgrade to pingora 0.8.1 or later (fix:  https://github.com/cloudflare/pingora/commit/d193c8d49b8b7c1c1ede93183759caa4f6906bbd ). When no H2Options are supplied, Pingora now advertises and enforces a 64 KiB decoded header-list limit and at most 100 concurrent streams per connection.&lt;/p&gt;
&lt;p&gt;*&lt;/p&gt;
&lt;p&gt;Applications that supply their own H2Options are not covered by these defaults and must set max_header_list_size and max_concurrent_streams explicitly (this also works on versions before 0.8.1), or, on 0.8…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;Before version 0.8.1, Pingora&amp;#39;s HTTP/2 server used the h2 crate&amp;#39;s default limits unless the application set its own 16 MiB decoded header-list size and no limit on concurrent streams. A remote, unauthenticated client can send 1-byte HPACK references to a near-empty header, making the server allocate hundreds of thousands of header fields per stream across an unlimited number of streams on one connection, and use HTTP/2 flow control to keep those streams open. This can exhaust memory and degrade or terminate the Pingora process.&lt;/p&gt;
&lt;p&gt;Impact&lt;/p&gt;
&lt;p&gt;Remote, unauthenticated denial of service against any Pingora service that terminates HTTP/2 (h2 or h2c) without explicitly setting max_header_list_size and max_concurrent_streams. The reporter showed that a single connection could get a Pingora process with a 2 GiB memory limit OOM-killed.&lt;/p&gt;
&lt;p&gt;Note that Cloudflare CDN customers were unaffected, as internal Pingora services at Cloudflare do not have HTTP/2 clients.&lt;/p&gt;
&lt;p&gt;Mitigation:&lt;/p&gt;
&lt;p&gt;*&lt;/p&gt;
&lt;p&gt;Upgrade to pingora 0.8.1 or later (fix:  https://github.com/cloudflare/pingora/commit/d193c8d49b8b7c1c1ede93183759caa4f6906bbd ). When no H2Options are supplied, Pingora now advertises and enforces a 64 KiB decoded header-list limit and at most 100 concurrent streams per connection.&lt;/p&gt;
&lt;p&gt;*&lt;/p&gt;
&lt;p&gt;Applications that supply their own H2Options are not covered by these defaults and must set max_header_list_size and max_concurrent_streams explicitly (this also works on versions before 0.8.1), or, on 0.8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-105297</guid>
    </item>
    <item>
      <title>GHSA-x6pg-x323-jhc4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x6pg-x323-jhc4</link>
      <description>&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;Before version 0.8.1, Pingora&amp;#39;s HTTP/2 server used the h2 crate&amp;#39;s default limits unless the application set its own 16 MiB decoded header-list size and no limit on concurrent streams. A remote, unauthenticated client can send 1-byte HPACK references to a near-empty header, making the server allocate hundreds of thousands of header fields per stream across an unlimited number of streams on one connection, and use HTTP/2 flow control to keep those streams open. This can exhaust memory and degrade or terminate the Pingora process.&lt;/p&gt;
&lt;p&gt;Impact&lt;/p&gt;
&lt;p&gt;Remote, unauthenticated denial of service against any Pingora service that terminates HTTP/2 (h2 or h2c) without explicitly setting max_header_list_size and max_concurrent_streams. The reporter showed that a single connection could get a Pingora process with a 2 GiB memory limit OOM-killed.&lt;/p&gt;
&lt;p&gt;Note that Cloudflare CDN customers were unaffected, as internal Pingora services at Cloudflare do not have HTTP/2 clients.&lt;/p&gt;
&lt;p&gt;Mitigation:&lt;/p&gt;
&lt;p&gt;*&lt;/p&gt;
&lt;p&gt;Upgrade to pingora 0.8.1 or later (fix:  https://github.com/cloudflare/pingora/commit/d193c8d49b8b7c1c1ede93183759caa4f6906bbd ). When no H2Options are supplied, Pingora now advertises and enforces a 64 KiB decoded header-list limit and at most 100 concurrent streams per connection.&lt;/p&gt;
&lt;p&gt;*&lt;/p&gt;
&lt;p&gt;Applications that supply their own H2Options are not covered by these defaults and must set max_header_list_size and max_concurrent_streams explicitly (this also works on versions before 0.8.1), or, on 0.8…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;Before version 0.8.1, Pingora&amp;#39;s HTTP/2 server used the h2 crate&amp;#39;s default limits unless the application set its own 16 MiB decoded header-list size and no limit on concurrent streams. A remote, unauthenticated client can send 1-byte HPACK references to a near-empty header, making the server allocate hundreds of thousands of header fields per stream across an unlimited number of streams on one connection, and use HTTP/2 flow control to keep those streams open. This can exhaust memory and degrade or terminate the Pingora process.&lt;/p&gt;
&lt;p&gt;Impact&lt;/p&gt;
&lt;p&gt;Remote, unauthenticated denial of service against any Pingora service that terminates HTTP/2 (h2 or h2c) without explicitly setting max_header_list_size and max_concurrent_streams. The reporter showed that a single connection could get a Pingora process with a 2 GiB memory limit OOM-killed.&lt;/p&gt;
&lt;p&gt;Note that Cloudflare CDN customers were unaffected, as internal Pingora services at Cloudflare do not have HTTP/2 clients.&lt;/p&gt;
&lt;p&gt;Mitigation:&lt;/p&gt;
&lt;p&gt;*&lt;/p&gt;
&lt;p&gt;Upgrade to pingora 0.8.1 or later (fix:  https://github.com/cloudflare/pingora/commit/d193c8d49b8b7c1c1ede93183759caa4f6906bbd ). When no H2Options are supplied, Pingora now advertises and enforces a 64 KiB decoded header-list limit and at most 100 concurrent streams per connection.&lt;/p&gt;
&lt;p&gt;*&lt;/p&gt;
&lt;p&gt;Applications that supply their own H2Options are not covered by these defaults and must set max_header_list_size and max_concurrent_streams explicitly (this also works on versions before 0.8.1), or, on 0.8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x6pg-x323-jhc4</guid>
    </item>
    <item>
      <title>RUSTSEC-2026-0389 — Pingora HTTP/2 server memory exhaustion through unbounded default header-list and concurrent-stream limits</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2026-0389</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: pingora-core&lt;/p&gt;
&lt;p&gt;Pingora versions prior to 0.8.1 used the h2 crate&amp;#39;s default HTTP/2 server limits, a 16 MiB decoded header-list size and no limit on concurrent streams, unless the application set its own. A remote, unauthenticated client can send 1-byte HPACK references to a near-empty header, making the server allocate hundreds of thousands of header fields per stream across an unlimited number of streams on one connection, and use HTTP/2 flow control to keep those streams open. This can exhaust memory and degrade or terminate the Pingora process.&lt;/p&gt;
&lt;p&gt;This affects any Pingora service that terminates HTTP/2 (h2 or h2c) without explicitly setting `max_header_list_size` and `max_concurrent_streams`. The reporter showed that a single connection could get a Pingora process with a 2 GiB memory limit OOM-killed.&lt;/p&gt;
&lt;p&gt;This flaw was corrected in commit d193c8d49b8b7c1c1ede93183759caa4f6906bbd. When no `H2Options` are supplied, Pingora now advertises and enforces a 64 KiB decoded header-list limit and at most 100 concurrent streams per connection. Users should upgrade to Pingora &amp;gt;= 0.8.1. Applications that supply their own `H2Options` are not covered by these defaults and must set `max_header_list_size` and `max_concurrent_streams` explicitly, or start from `pingora_core::protocols::http::v2::server::default_h2_options()`. `H2Options::default()` does not include these limits.&lt;/p&gt;
&lt;p&gt;Note: Cloudflare CDN customers were unaffected, as internal Pingora services at Cloudflare do not have HTTP/2 clients.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: pingora-core&lt;/p&gt;
&lt;p&gt;Pingora versions prior to 0.8.1 used the h2 crate&amp;#39;s default HTTP/2 server limits, a 16 MiB decoded header-list size and no limit on concurrent streams, unless the application set its own. A remote, unauthenticated client can send 1-byte HPACK references to a near-empty header, making the server allocate hundreds of thousands of header fields per stream across an unlimited number of streams on one connection, and use HTTP/2 flow control to keep those streams open. This can exhaust memory and degrade or terminate the Pingora process.&lt;/p&gt;
&lt;p&gt;This affects any Pingora service that terminates HTTP/2 (h2 or h2c) without explicitly setting `max_header_list_size` and `max_concurrent_streams`. The reporter showed that a single connection could get a Pingora process with a 2 GiB memory limit OOM-killed.&lt;/p&gt;
&lt;p&gt;This flaw was corrected in commit d193c8d49b8b7c1c1ede93183759caa4f6906bbd. When no `H2Options` are supplied, Pingora now advertises and enforces a 64 KiB decoded header-list limit and at most 100 concurrent streams per connection. Users should upgrade to Pingora &amp;gt;= 0.8.1. Applications that supply their own `H2Options` are not covered by these defaults and must set `max_header_list_size` and `max_concurrent_streams` explicitly, or start from `pingora_core::protocols::http::v2::server::default_h2_options()`. `H2Options::default()` does not include these limits.&lt;/p&gt;
&lt;p&gt;Note: Cloudflare CDN customers were unaffected, as internal Pingora services at Cloudflare do not have HTTP/2 clients.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2026-0389</guid>
    </item>
  </channel>
</rss>
