CVE-2025-61919: Rack is vulnerable to a memory-exhaustion DoS through unbounded URL-encoded body parsing

Published Oct 10, 2025
·
Updated

Summary

Rack::Request#POST reads the entire request body into memory for Content-Type: application/x-www-form-urlencoded, calling rack.input.read(nil) without enforcing a length or cap. Large request bodies can therefore be buffered completely into process memory before parsing, leading to denial of service (DoS) through memory exhaustion.

Details

When handling non-multipart form submissions, Rack’s request parser performs:

ruby formvars = getheader(RACKINPUT).read

Since read is called with no argument, the entire request body is loaded into a Ruby String. This occurs before query parameter parsing or enforcement of any paramslimit. As a result, Rack applications without an upstream body-size limit can experience unbounded memory allocation proportional to request size.

Impact

Attackers can send large application/x-www-form-urlencoded bodies to consume process memory, causing slowdowns or termination by the operating system (OOM). The effect scales linearly with request size and concurrency. Even with parsing limits configured, the issue occurs before those limits are enforced.

Mitigation

Update to a patched version of Rack that enforces form parameter limits using queryparser.bytesizelimit, preventing unbounded reads of application/x-www-form-urlencoded bodies. Enforce strict maximum body size at the proxy or web server layer (e.g., Nginx clientmaxbodysize, Apache LimitRequestBody).

Other sources

Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, Rack::Request#POST reads the entire request body into memory for Content-Type: application/x-www-form-urlencoded, calling rack.input.read(nil) without enforcing a length or cap. Large request bodies can therefore be buffered completely into process memory before parsing, leading to denial of service (DoS) through memory exhaustion. Users should upgrade to Rack version 2.2.20, 3.1.18, or 3.2.3, anu of which enforces form parameter limits using queryparser.bytesizelimit, preventing unbounded reads of application/x-www-form-urlencoded bodies. Additionally, enforce strict maximum body size at the proxy or web server layer (e.g., Nginx clientmaxbodysize, Apache LimitRequestBody).

MITRE

Affected Software

7 affected componentsFixes available
rubygems/rack>=3.2<3.2.3
3.2.3
rubygems/rack>=3.0<3.1.18
3.1.18
rubygems/rack<2.2.20
2.2.20
Rack Rack Ruby<2.2.20
Rack Rack Ruby>=3.0.0<3.1.18
Rack Rack Ruby>=3.2.0<3.2.3
IBM Aspera Console<=3.4.7

Event History

Oct 10, 2025
Advisory Published
via GitHub·05:33 PM
Data Sourced
via GitHub·05:33 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·07:22 PM
Data Sourced
via MITRE·07:22 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·08:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
RemedyAffected Software
Jan 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-61919?

CVE-2025-61919 has a medium severity due to the potential for denial-of-service attacks from excessive memory usage.

2

How do I fix CVE-2025-61919?

To fix CVE-2025-61919, upgrade to Rack version 3.2.3, 3.1.18, or 2.2.20.

3

What types of requests are affected by CVE-2025-61919?

CVE-2025-61919 affects requests with the Content-Type set to application/x-www-form-urlencoded.

4

What are the potential impacts of CVE-2025-61919?

The potential impacts of CVE-2025-61919 include excessive memory consumption leading to application crashes or slowdowns.

5

Is CVE-2025-61919 specific to a particular software version?

Yes, CVE-2025-61919 specifically affects Rack versions prior to 3.2.3, 3.1.18, and 2.2.20.

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