UBUNTU-CVE-2026-26962: Medium severity ubuntu/ruby-rack vulnerability

Published Apr 2, 2026
·
Updated

Rack is a modular Ruby web server interface. From version 3.2.0 to before version 3.2.6, Rack::Multipart::Parser unfolds folded multipart part headers incorrectly. When a multipart header contains an obs-fold sequence, Rack preserves the embedded CRLF in parsed parameter values such as filename or name instead of removing the folded line break during unfolding. As a result, applications that later reuse those parsed values in HTTP response headers may be vulnerable to downstream header injection or response splitting. This issue has been patched in version 3.2.6.

Affected Software

8 affected componentsFixes available
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack<2.2.7-1ubuntu0.7
2.2.7-1ubuntu0.7
ubuntu/ruby-rack<3.1.16-0.1ubuntu0.3
3.1.16-0.1ubuntu0.3
ubuntu/ruby-rack*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/ruby-rack to a version that resolves this vulnerability.

    Fixed in 2.2.7-1ubuntu0.7
  2. Upgrade

    Upgrade ubuntu/ruby-rack to a version that resolves this vulnerability.

    Fixed in 3.1.16-0.1ubuntu0.3
  3. Upgrade

    Upgrade Rack to a version that resolves this vulnerability.

    Fixed in 3.2.6

Event History

Apr 2, 2026
CVE Published
via OSV·06:16 PM
Data Sourced
via OSV·06:16 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are exposed to practical exploitation?

Applications using Rack versions 3.2.0 through 3.2.5 are exposed if they accept multipart requests and later place parsed multipart parameter values, such as filename or name, into HTTP response headers.

2

What does an attacker need to send?

An attacker needs to submit a multipart request containing an obs-fold sequence in a part header. No privileges or user interaction are required, but exploitation depends on the application reusing the affected parsed value in a response header.

3

Are applications affected simply by running a vulnerable Rack version?

No. The parser behavior exists in the affected versions, but downstream header injection or response splitting requires application code to reuse a parsed multipart value in an HTTP response header.

4

What is the remediation?

Update Rack to version 3.2.6 or later. If updating cannot happen immediately, avoid using multipart-derived filename or name values in HTTP response headers.

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