CVE-2026-26961: Rack's greedy multipart boundary parsing can cause parser differentials and WAF bypass.
Summary Rack::Multipart::Parser extracts the boundary parameter from multipart/form-data using a greedy regular expression. When a Content-Type header contains multiple boundary parameters, Rack selects the last one rather than the first.
Published Apr 2, 2026 · Updated May 13, 2026
Affected packages
rack
- Ecosystem
- RubyGems
- Affected
- < 2.2.23
- Fixed in
- 2.2.23
- Check
bundle info rack
rack
- Ecosystem
- RubyGems
- Affected
- >= 3.0.0.beta1, < 3.1.21
- Fixed in
- 3.1.21
- Check
bundle info rack
rack
- Ecosystem
- RubyGems
- Affected
- >= 3.2.0, < 3.2.6
- Fixed in
- 3.2.6
- Check
bundle info rack
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Rack::Multipart::Parser extracts the boundary parameter from multipart/form-data using a greedy regular expression. When a Content-Type header contains multiple boundary parameters, Rack selects the last one rather than the first.
In deployments where an upstream proxy, WAF, or intermediary interprets the first boundary parameter, this mismatch can allow an attacker to smuggle multipart content past upstream inspection and have Rack parse a different body structure than the intermediary validated.
Details
Rack identifies the multipart boundary using logic equivalent to:
MULTIPART = %r|\Amultipart/.*boundary=\"?([^\";,]+)\"?|niBecause the expression is greedy, it matches the last boundary= parameter in a header such as:
Content-Type: multipart/form-data; boundary=safe; boundary=maliciousAs a result, Rack parses the request body using malicious, while another component may interpret the same header using safe.
This creates an interpretation conflict. If an upstream WAF or proxy inspects multipart parts using the first boundary and Rack later parses the body using the last boundary, a client may be able to place malicious form fields or uploaded content in parts that Rack accepts but the upstream component did not inspect as intended.
This issue is most relevant in layered deployments where security decisions are made before the request reaches Rack.
Impact
Applications that accept multipart/form-data uploads behind an inspecting proxy or WAF may be affected.
In such deployments, an attacker may be able to bypass upstream filtering of uploaded files or form fields by sending a request with multiple boundary parameters and relying on the intermediary and Rack to parse the request differently.
The practical impact depends on deployment architecture. If no upstream component relies on a different multipart interpretation, this behavior may not provide meaningful additional attacker capability.
Mitigation
- Update to a patched version of Rack that rejects ambiguous multipart
Content-Typeheaders or parses duplicateboundaryparameters consistently. - Reject requests containing multiple
boundaryparameters. - Normalize or regenerate multipart metadata at the trusted edge before forwarding requests to Rack.
- Avoid relying on upstream inspection of malformed multipart requests unless duplicate parameter handling is explicitly consistent across components.
Credited to CodeByMoriarty, jeremyevans, ioquatix.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesCVE-2026-125108
Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass
low3.7Nov 10, 2026CVE-2026-125109
Rack: Rack::Request#host_with_port (and #base_url / #url) return the raw invalid Host header — incomplete fix of CVE-2026-34835
medium4.8Nov 10, 2026CVE-2026-125110
Rack: Rack::Static header_rules bypass via dot-segment normalization mismatch
medium5.3Nov 10, 2026CVE-2026-125111
Rack: Multipart parsing allows DoS via unbounded scan buffer growth
high7.5Nov 10, 2026CVE-2026-26962
Rack's improper unfolding of folded multipart headers preserves CRLF in parsed parameter values
medium4.8Apr 2, 2026CVE-2026-32762
Rack: Forwarded Header semicolon injection enables Host and Scheme spoofing
medium4.8Apr 2, 2026
