<?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>Fri, 02 Oct 2026 17:18:46 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-342253</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-342253</link>
      <description>EUVD-2026-342253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-342253</guid>
    </item>
    <item>
      <title>fkie_cve-2026-65624</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-65624</link>
      <description>&lt;p&gt;Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.&lt;/p&gt;
&lt;p&gt;The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (&amp;#34;, &amp;#34; for regular headers, &amp;#34;; &amp;#34; for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process&amp;#39;s binary memory to arbitrary size within the request window.&lt;/p&gt;
&lt;p&gt;The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.&lt;/p&gt;
&lt;p&gt;This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.&lt;/p&gt;
&lt;p&gt;The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (&amp;#34;, &amp;#34; for regular headers, &amp;#34;; &amp;#34; for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process&amp;#39;s binary memory to arbitrary size within the request window.&lt;/p&gt;
&lt;p&gt;The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.&lt;/p&gt;
&lt;p&gt;This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-65624</guid>
    </item>
    <item>
      <title>GHSA-v9x8-262p-f2g5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v9x8-262p-f2g5</link>
      <description>&lt;p&gt;Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.&lt;/p&gt;
&lt;p&gt;The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (&amp;#34;, &amp;#34; for regular headers, &amp;#34;; &amp;#34; for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process&amp;#39;s binary memory to arbitrary size within the request window.&lt;/p&gt;
&lt;p&gt;The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.&lt;/p&gt;
&lt;p&gt;This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.&lt;/p&gt;
&lt;p&gt;The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (&amp;#34;, &amp;#34; for regular headers, &amp;#34;; &amp;#34; for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process&amp;#39;s binary memory to arbitrary size within the request window.&lt;/p&gt;
&lt;p&gt;The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.&lt;/p&gt;
&lt;p&gt;This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v9x8-262p-f2g5</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-65624 — Cowboy HTTP/1.1 max_headers Bypass via Duplicate Header Names Enables Memory Exhaustion</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-65624</link>
      <description>msrc_CVE-2026-65624</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-65624</guid>
    </item>
    <item>
      <title>RHSA-2026:47231 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:47231</link>
      <description>&lt;p&gt;cowlib: Cowlib: Denial of Service due to unbounded HPACK/QPACK prefixed-integer decoding cowboy: Cowboy: Denial of Service via HTTP/1.1 duplicate header names&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;cowlib: Cowlib: Denial of Service due to unbounded HPACK/QPACK prefixed-integer decoding cowboy: Cowboy: Denial of Service via HTTP/1.1 duplicate header names&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:47231</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-65624</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-65624</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: rabbitmq-server, Ubuntu:16.04:LTS: erlang-cowboy, Ubuntu:18.04:LTS: rabbitmq-server, Ubuntu:18.04:LTS: erlang-cowboy, Ubuntu:20.04:LTS: rabbitmq-server, Ubuntu:20.04:LTS: erlang-cowboy, Ubuntu:22.04:LTS: erlang-cowboy, Ubuntu:22.04:LTS: rabbitmq-server, Ubuntu:24.04:LTS: erlang-cowboy, Ubuntu:24.04:LTS: rabbitmq-server and 2 more&lt;/p&gt;
&lt;p&gt;Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1. The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (&amp;#34;, &amp;#34; for regular headers, &amp;#34;; &amp;#34; for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process&amp;#39;s binary memory to arbitrary size within the request window. The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions. This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: rabbitmq-server, Ubuntu:16.04:LTS: erlang-cowboy, Ubuntu:18.04:LTS: rabbitmq-server, Ubuntu:18.04:LTS: erlang-cowboy, Ubuntu:20.04:LTS: rabbitmq-server, Ubuntu:20.04:LTS: erlang-cowboy, Ubuntu:22.04:LTS: erlang-cowboy, Ubuntu:22.04:LTS: rabbitmq-server, Ubuntu:24.04:LTS: erlang-cowboy, Ubuntu:24.04:LTS: rabbitmq-server and 2 more&lt;/p&gt;
&lt;p&gt;Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1. The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (&amp;#34;, &amp;#34; for regular headers, &amp;#34;; &amp;#34; for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process&amp;#39;s binary memory to arbitrary size within the request window. The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions. This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-65624</guid>
    </item>
  </channel>
</rss>
