<?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://vulnerability.circl.lu</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 08:45:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-61772 — Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion)</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-61772</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rack&lt;/p&gt;
&lt;p&gt;Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, `Rack::Multipart::Parser` can accumulate unbounded data when a multipart part’s header block never terminates with the required blank line (`CRLFCRLF`). The parser keeps appending incoming bytes to memory without a size cap, allowing a remote attacker to exhaust memory and cause a denial of service (DoS). Attackers can send incomplete multipart headers to trigger high memory use, leading to process termination (OOM) or severe slowdown. The effect scales with request size limits and concurrency. All applications handling multipart uploads may be affected. Versions 2.2.19, 3.1.17, and 3.2.2 cap per-part header size (e.g., 64 KiB). As a workaround, restrict maximum request sizes at the proxy or web server layer (e.g., Nginx `client_max_body_size`).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rack&lt;/p&gt;
&lt;p&gt;Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, `Rack::Multipart::Parser` can accumulate unbounded data when a multipart part’s header block never terminates with the required blank line (`CRLFCRLF`). The parser keeps appending incoming bytes to memory without a size cap, allowing a remote attacker to exhaust memory and cause a denial of service (DoS). Attackers can send incomplete multipart headers to trigger high memory use, leading to process termination (OOM) or severe slowdown. The effect scales with request size limits and concurrency. All applications handling multipart uploads may be affected. Versions 2.2.19, 3.1.17, and 3.2.2 cap per-part header size (e.g., 64 KiB). As a workaround, restrict maximum request sizes at the proxy or web server layer (e.g., Nginx `client_max_body_size`).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-61772</guid>
    </item>
    <item>
      <title>GHSA-wpv5-97wm-hp9c — Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion)</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-wpv5-97wm-hp9c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: rack&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Rack::Multipart::Parser` can accumulate unbounded data when a multipart part’s header block never terminates with the required blank line (`CRLFCRLF`). The parser keeps appending incoming bytes to memory without a size cap, allowing a remote attacker to exhaust memory and cause a denial of service (DoS).&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;While reading multipart headers, the parser waits for `CRLFCRLF` using:&lt;/p&gt;
&lt;p&gt;```ruby
@sbuf.scan_until(/(.*?\r\n)\r\n/m)
```&lt;/p&gt;
&lt;p&gt;If the terminator never appears, it continues appending data (`@sbuf.concat(content)`) indefinitely. There is no limit on accumulated header bytes, so a single malformed part can consume memory proportional to the request body size.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Attackers can send incomplete multipart headers to trigger high memory use, leading to process termination (OOM) or severe slowdown. The effect scales with request size limits and concurrency. All applications handling multipart uploads may be affected.&lt;/p&gt;
&lt;p&gt;## Mitigation&lt;/p&gt;
&lt;p&gt;* Upgrade to a patched Rack version that caps per-part header size (e.g., 64 KiB).
* Until then, restrict maximum request sizes at the proxy or web server layer (e.g., Nginx `client_max_body_size`).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: rack&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Rack::Multipart::Parser` can accumulate unbounded data when a multipart part’s header block never terminates with the required blank line (`CRLFCRLF`). The parser keeps appending incoming bytes to memory without a size cap, allowing a remote attacker to exhaust memory and cause a denial of service (DoS).&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;While reading multipart headers, the parser waits for `CRLFCRLF` using:&lt;/p&gt;
&lt;p&gt;```ruby
@sbuf.scan_until(/(.*?\r\n)\r\n/m)
```&lt;/p&gt;
&lt;p&gt;If the terminator never appears, it continues appending data (`@sbuf.concat(content)`) indefinitely. There is no limit on accumulated header bytes, so a single malformed part can consume memory proportional to the request body size.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Attackers can send incomplete multipart headers to trigger high memory use, leading to process termination (OOM) or severe slowdown. The effect scales with request size limits and concurrency. All applications handling multipart uploads may be affected.&lt;/p&gt;
&lt;p&gt;## Mitigation&lt;/p&gt;
&lt;p&gt;* Upgrade to a patched Rack version that caps per-part header size (e.g., 64 KiB).
* Until then, restrict maximum request sizes at the proxy or web server layer (e.g., Nginx `client_max_body_size`).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-wpv5-97wm-hp9c</guid>
    </item>
  </channel>
</rss>
