GHSA-p8x9-v4hv-2w4g: Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass

Published Nov 9, 2026
·
Updated

Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parseboundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.

Affected Software

1 affected component
rubygems/rack<2.2.25, <3.1.23, <3.2.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Rack to a version that resolves this vulnerability.

    Fixed in 2.2.25
  2. Upgrade

    Upgrade Rack to a version that resolves this vulnerability.

    Fixed in 3.1.23
  3. Upgrade

    Upgrade Rack to a version that resolves this vulnerability.

    Fixed in 3.2.8

Event History

Nov 9, 2026
CVE Published
via OSV·09:55 PM
Data Sourced
via OSV·09:55 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments using Rack versions earlier than 2.2.25, 3.1.23, or 3.2.8 are affected when requests pass through an intermediary such as a proxy or web application firewall that derives multipart boundaries differently from Rack.

2

What does an attacker need to exploit the bypass?

An attacker needs to send a multipart request with a Content-Type header containing a leading empty or quoted boundary parameter followed by another boundary parameter. The attack relies on Rack accepting the later parameter while a conforming intermediary derives a different boundary.

3

What is the impact if exploitation succeeds?

Form fields or file uploads can reach the application without receiving the intended proxy or web application firewall inspection. The provided severity vector indicates integrity impact only, with no stated confidentiality or availability impact.

4

How can this be remediated?

Upgrade Rack to version 2.2.25, 3.1.23, or 3.2.8, depending on the supported release line in use.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203