Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion)
Published 7 Oct 2025 · Updated 10 Sept 2026
Is your project on an affected rack?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <2.2.19
- Fixed in
- 2.2.19
bundle update --conservative rack # Gemfile: '>= 2.2.19'- Affected
- >=3.1 <3.1.17
- Fixed in
- 3.1.17
bundle update --conservative rack # Gemfile: '>= 3.1.17'- Affected
- >=3.2 <3.2.2
- Fixed in
- 3.2.2
bundle update --conservative rack # Gemfile: '>= 3.2.2'Details
Summary
Rack::Multipart::Parser buffers the entire multipart preamble (bytes before the first boundary) in memory without any size limit. A client can send a large preamble followed by a valid boundary, causing significant memory use and potential process termination due to out-of-memory (OOM) conditions.
Details
While searching for the first boundary, the parser appends incoming data into a shared buffer (@sbuf.concat(content)) and scans for the boundary pattern:
@sbuf.scan_until(@body_regex)
If the boundary is not yet found, the parser continues buffering data indefinitely. There is no trimming or size cap on the preamble, allowing attackers to send arbitrary amounts of data before the first boundary.
Impact
Remote attackers can trigger large transient memory spikes by including a long preamble in multipart/form-data requests. The impact scales with allowed request sizes and concurrency, potentially causing worker crashes or severe slowdown due to garbage collection.
Mitigation
- Upgrade: Use a patched version of Rack that enforces a preamble size limit (e.g., 16 KiB) or discards preamble data entirely per RFC 2046 § 5.1.1.
- Workarounds:
- Limit total request body size at the proxy or web server level.
- Monitor memory and set per-process limits to prevent OOM conditions.
Is GHSA-p543-xpfm-54cp in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected rack, and gives you the command that fixes it.
More advisories for rack
- HighCVE-2026-125111Rack: Multipart parsing allows DoS via unbounded scan buffer growth · 10 Nov 2026
- LowCVE-2026-125108Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass · 10 Nov 2026
- MediumCVE-2026-125109Rack: Rack::Request#host_with_port (and #base_url / #url) return the raw invalid Host header — incomplete fix of CVE-2026-34835 · 10 Nov 2026
- MediumCVE-2026-125110Rack: Rack::Static header_rules bypass via dot-segment normalization mismatch · 10 Nov 2026
- MediumCVE-2026-34835Rack::Request accepts invalid Host characters, enabling host allowlist bypass · 2 Apr 2026
- MediumCVE-2026-34831Rack has Content-Length mismatch in Rack::Files error responses · 2 Apr 2026
References
- Linkgithub.com/rack/rack/security/advisories/GHSA-p543-xpfm-54cp
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-61770
- Linkgithub.com/rack/rack/commit/589127f4ac8b5cf11cf88fb0cd116ffed4d2181e
- Linkgithub.com/rack/rack/commit/d869fed663b113b95a74ad53e1b5cae6ab31f29e
- Linkgithub.com/rack/rack/commit/e08f78c656c9394d6737c022bde087e0f33336fd
- Packagegithub.com/rack/rack
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2025-61770.yml
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.