NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 75.9% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: rack rack 3.0.9.1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to rack rack 3.0.9.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Feb 28, 2024
Updated: Jun 17, 2026
EPSS: 1.6% · 75th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.6%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.5
CNA · GitHub_M: 5.8; 1.7 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
rack	rack	cpe:2.3:a:rack:rack
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux10.0
rack rack1.3.0 and later · before 2.2.8.1
rack rack3.0.0 and later · before 3.0.9.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

rack rack
- >= 3.0.0, < 3.0.9.1, >= 1.3.0, < 2.2.8.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:8	pcs	before 0.10.18-2.el8_10	0.10.18-2.el8_10
AlmaLinux:8	pcs-snmp	before 0.10.18-2.el8_10	0.10.18-2.el8_10
AlmaLinux:9	pcs	before 0.11.7-2.el9_4	0.11.7-2.el9_4
AlmaLinux:9	pcs-snmp	before 0.11.7-2.el9_4	0.11.7-2.el9_4
Debian:10	ruby-rack	before 2.0.6-3+deb10u4	2.0.6-3+deb10u4
Debian:11	ruby-rack	before 2.1.4-3+deb11u2	2.1.4-3+deb11u2
Debian:12	ruby-rack	before 2.2.6.4-1+deb12u1	2.2.6.4-1+deb12u1
Debian:13	ruby-rack	before 2.2.7-1.1	2.2.7-1.1
openSUSE:Leap 15.5	rubygem-rack	before 2.0.8-150000.3.21.2	2.0.8-150000.3.21.2
openSUSE:Tumbleweed	rubygem-rack	before 3.1.18-1.3	3.1.18-1.3
openSUSE:Tumbleweed	rubygem-rack	before 3.0.9.1-1.1	3.0.9.1-1.1
openSUSE:Tumbleweed	rubygem-rack	before 3.1.12-1.1	3.1.12-1.1
openSUSE:Tumbleweed	rubygem-rack-2.2	before 2.2.22-1.1	2.2.22-1.1
openSUSE:Tumbleweed	rubygem-rack-2.2	before 2.2.8.1-1.1	2.2.8.1-1.1
openSUSE:Tumbleweed	rubygem-rack-2.2	before 2.2.11-1.1	2.2.11-1.1
Red Hat:enterprise_linux:8::highavailability	pcs	before 0:0.10.18-2.el8_10	0:0.10.18-2.el8_10
Red Hat:enterprise_linux:8::highavailability	pcs-snmp	before 0:0.10.18-2.el8_10	0:0.10.18-2.el8_10
Red Hat:enterprise_linux:9::highavailability	pcs	before 0:0.11.7-2.el9_4	0:0.11.7-2.el9_4
Red Hat:enterprise_linux:9::highavailability	pcs-snmp	before 0:0.11.7-2.el9_4	0:0.11.7-2.el9_4
Red Hat:rhel_aus:8.4::highavailability	pcs	before 0:0.10.8-1.el8_4.5	0:0.10.8-1.el8_4.5
Red Hat:rhel_aus:8.4::highavailability	pcs-snmp	before 0:0.10.8-1.el8_4.5	0:0.10.8-1.el8_4.5
Red Hat:rhel_e4s:8.2::highavailability	pcs	before 0:0.10.4-6.el8_2.5	0:0.10.4-6.el8_2.5
Red Hat:rhel_e4s:8.2::highavailability	pcs-snmp	before 0:0.10.4-6.el8_2.5	0:0.10.4-6.el8_2.5
Red Hat:rhel_eus:8.6::highavailability	pcs	before 0:0.10.12-6.el8_6.5	0:0.10.12-6.el8_6.5

+17

Same product

rack: all records

Other highest-scoring records for the same primary product.

CVE-2024-25126Rack ReDos in content type parsing (2nd degree polynomial)
41Plan
CVE-2024-26146Possible Denial of Service Vulnerability in Rack Header Parsing
31Monitor
CVE-2023-27530A DoS vulnerability exists in Rack <v3.0.4.2, <v2.2.6.3, <v2.1.4.3 and <v2.0.9.3 within in the Multipart MIME parsing code in which could al
31Monitor

Published before and after this one in the same product

← EarlierCVE-2022-44571Feb 9, 2023 · There is a denial of service vulnerability in the Content-Disposition parsingcomponent of Rack fixed in 2.0.9.2, 2.1.4.2, 2.2.4.1, 3.0.0.1.
30Monitor
← EarlierCVE-2022-44572Feb 9, 2023 · A denial of service vulnerability in the multipart parsing component of Rack fixed in 2.0.9.2, 2.1.4.2, 2.2.4.1 and 3.0.0.1 could allow an a
30Monitor
Later →CVE-2024-39316Jul 2, 2024 · Rack ReDoS Vulnerability in HTTP Accept Headers Parsing
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
rack rack	3.0.9.1 · description	Vendor (CNA)
almalinux:pcs	0.11.7-2.el9_4 · AlmaLinux:9	Package registry (OSV)
almalinux:pcs-snmp	0.11.7-2.el9_4 · AlmaLinux:9	Package registry (OSV)
debian:ruby-rack	2.2.6.4-1+deb12u1 · Debian:12	Package registry (OSV)
opensuse:rubygem-rack	2.0.8-150000.3.21.2 · openSUSE:Leap 15.5	Package registry (OSV)
opensuse:rubygem-rack-2.2	2.2.8.1-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:pcs	0:0.11.1-10.el9_0.5 · Red Hat:rhel_eus:9.0::highavailability	Package registry (OSV)
red hat:pcs-snmp	0:0.11.1-10.el9_0.5 · Red Hat:rhel_eus:9.0::highavailability	Package registry (OSV)
red hat:python-pulp-container	0:2.16.9-2.el8pc · Red Hat:satellite_capsule:6.15::el8	Package registry (OSV)
red hat:python3.11-pulp-container	0:2.16.9-2.el8pc · Red Hat:satellite_capsule:6.15::el8	Package registry (OSV)
red hat:rubygem-activestorage	0:6.1.7.7-1.el8sat · Red Hat:satellite:6.15::el8	Package registry (OSV)
red hat:rubygem-rack	0:2.2.8.1-1.el8sat · Red Hat:satellite_capsule:6.15::el8	Package registry (OSV)
rocky linux:pcs	0:0.10.18-2.el8_10 · Rocky Linux:8	Package registry (OSV)
RubyGems:rack	2.2.8.1	Package registry (OSV)
RubyGems:rack	3.0.9.1	Package registry (OSV)
suse:rubygem-rack	2.0.8-150000.3.21.2 · SUSE:Linux Enterprise High Availability Extension 15 SP2	Package registry (OSV)
suse:rubygem-rack-1_4	1.4.5-9.3.1 · SUSE:Linux Enterprise Module for Containers 12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2023-27530355 days apartA DoS vulnerability exists in Rack <v3.0.4.2, <v2.2.6.3, <v2.1.4.3 and <v2.0.9.3 within in the Multipart MIME parsing code in which could al
31Monitor
CVE-2022-44570384 days apartA denial of service vulnerability in the Range header parsing component of Rack >= 1.5.0.
30Monitor
CVE-2022-44571384 days apartThere is a denial of service vulnerability in the Content-Disposition parsingcomponent of Rack fixed in 2.0.9.2, 2.1.4.2, 2.2.4.1, 3.0.0.1.
30Monitor
CVE-2022-44572384 days apartA denial of service vulnerability in the multipart parsing component of Rack fixed in 2.0.9.2, 2.1.4.2, 2.2.4.1 and 3.0.0.1 could allow an a
30Monitor
CVE-2025-46727434 days apartUnbounded-Parameter DoS in Rack::QueryParser
30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0151 · Feb 29, 2024(Ruby Güvenlik Zafiyeti)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/rack/rack/commit/4849132bef471adb21131980df745f4bb84de2d9

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records