Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass
GHSA-p8x9-v4hv-2w4g · CVE-2026-125108
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Summary
The guard added for CVE-2026-26961 (GHSA-vgpv-f759-9wx3), which rejects multipart requests with more than one boundary parameter, only inspects the part of the Content-Type header after the boundary it extracts. A Content-Type whose first boundary parameter is empty or begins with a quote, semicolon, or comma is skipped by the extraction pattern, so a second boundary parameter is accepted silently and Rack parses the body with a boundary that a conforming parser would not derive from the header.
Details
Rack::Multipart::Parser.parse_boundary extracts the boundary with a regular expression that uses a lazy prefix and a value class excluding ", ;, and ,. For a header such as multipart/form-data; boundary=";boundary=AaB03x" or multipart/form-data; boundary=; boundary=AaB03x, the pattern skips the first boundary= and anchors on the second, and the subsequent check for another boundary= in the remaining text finds nothing. Rack then uses AaB03x.
RFC 9110 parses the first header as a single parameter whose value is ;boundary=AaB03x, which is not a legal boundary under RFC 2046, so the only conformant outcome is rejection. Inspecting intermediaries that implement the standard grammar, such as ModSecurity, see a different boundary or no multipart body at all.
The fix counts boundary= occurrences across the entire header value and rejects the request when there is more than one.
Impact
As with CVE-2026-26961, an attacker can craft a multipart request that a web application firewall or other inspecting proxy in front of a Rack application interprets differently from Rack, so form fields and file uploads reach the application without inspection. Rack itself grants no capability beyond that of a well-formed request with the same body. All supported versions, including 2.2, are affected.
Mitigation
- Update to a patched version of Rack.
- Reject requests whose
Content-Typecontains more than oneboundaryparameter at the reverse proxy.
References
- WEB https://github.com/rack/rack/security/advisories/GHSA-p8x9-v4hv-2w4g
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-125108
- WEB https://github.com/rack/rack/commit/19a1a19cb4da97d61c8d5effeb2e927c44370ae9
- WEB https://github.com/rack/rack/commit/a29512324265790a5536b830490075d0d79323be
- WEB https://github.com/rack/rack/commit/d5e928b803da30b8e40171dbd4be39bed7daa6fa
- PACKAGE https://github.com/rack/rack
- WEB https://github.com/rack/rack/releases/tag/v2.2.25
- WEB https://github.com/rack/rack/releases/tag/v3.1.23
- WEB https://github.com/rack/rack/releases/tag/v3.2.8
- WEB https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/GHSA-p8x9-v4hv-2w4g.yml
Ready to move
Start Securing
Free, no credit card | First findings in minutes