# CVE-2024-26141: Possible DoS Vulnerability with Range Header in Rack

> Attackers can cause denial of service by sending crafted Range headers to Rack-based applications, leading to unexpectedly large responses.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Feb 2024
- **Updated:** 13 Feb 2025
- **Also known as:** DEBIAN-CVE-2024-26141, GHSA-xj5v-6v4g-jfw6, UBUNTU-CVE-2024-26141

## What is CVE-2024-26141?

CVE-2024-26141 is a medium-severity denial of service vulnerability in Debian Debian Linux, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rack is a modular Ruby web server interface. Carefully crafted Range headers can cause a server to respond with an unexpectedly large response. Responding with such large responses could lead to a denial of service issue. Vulnerable applications will use the `Rack::File` middleware or the `Rack::Utils.byte_ranges` methods (this includes Rails applications). The vulnerability is fixed in 3.0.9.1 and 2.2.8.1.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-26141?

4 open source packages ship an affected version, including rack. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rack` | RubyGems | From 1.3.0 | 2.2.8.1 |
| `rack` | RubyGems | From 1.3.0 | 2.2.8.1 |
| `rack` | RubyGems | From 3.0.0 | 3.0.9.1 |
| `rack` | RubyGems | From 3.0.0 | 3.0.9.1 |

Products: Debian Debian Linux, Rack Rack.

## How do I fix CVE-2024-26141?

Upgrade rack to a fixed version for your release line: 2.2.8.1 or 3.0.9.1.

## Is CVE-2024-26141 being exploited?

There is no known exploitation of CVE-2024-26141 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26141 and fix it if it is affected.

What it is: CVE-2024-26141 is a medium-severity denial of service vulnerability in Debian Debian Linux, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-26141 in the wild and no public exploit code.

Affected packages and fixed versions:
- rack (RubyGems): affected from 1.3.0; fixed in 2.2.8.1
- rack (RubyGems): affected from 1.3.0; fixed in 2.2.8.1
- rack (RubyGems): affected from 3.0.0; fixed in 3.0.9.1
- rack (RubyGems): affected from 3.0.0; fixed in 3.0.9.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26141/ (Markdown: https://insights.sbomify.com/CVE-2024-26141/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26141
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26141
- OSV: https://osv.dev/vulnerability/CVE-2024-26141

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26141/
Summaries are generated and may contain mistakes; the official description above is the record.