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

Published Nov 12, 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 can retain parsed data in its internal StringScanner buffer when reads end inside or immediately after multipart headers. An unauthenticated attacker can align many small parts with rack.multipart.buffersize boundaries so the buffer grows with the request despite per-field, header, and preamble limits, causing a worker to exhaust memory. The attack requires only a well-formed multipart body and affects applications that parse multipart requests. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.

Affected Software

8 affected components
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack*
ubuntu/ruby-rack*

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 12, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications using affected Rack versions that parse multipart requests are exposed. The issue affects Rack versions before 2.2.25, 3.1.23, and 3.2.8.

2

What does an attacker need to exploit it?

An attacker needs only to send a well-formed multipart request body. No authentication is required; the request is constructed with many small parts aligned to rack.multipart.buffer_size boundaries.

3

Are Rack multipart limits sufficient to prevent exploitation?

No. The buffer can grow despite per-field, header, and preamble limits when reads end inside or immediately after multipart headers.

4

What is the impact of a successful attack?

A worker can exhaust available memory while parsing the request, resulting in denial of service.

5

How can this be remediated?

Upgrade Rack to version 2.2.25, 3.1.23, or 3.2.8, as appropriate for the deployed release line.

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