dbcve.org
RackApplication

CVE-2024-26146

HIGH · 7.5 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 2.0.9.4 / 2.1.4.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Rack is a modular Ruby web server interface. Carefully crafted headers can cause header parsing in Rack to take longer than expected resulting in a possible denial of service issue. Accept and Forwarded headers are impacted. Ruby 3.2 has mitigations for this problem, so Rack applications using Ruby 3.2 or newer are unaffected. This vulnerability is fixed in 2.0.9.4, 2.1.4.4, 2.2.8.1, and 3.0.9.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RackApplication
Affected:>= 0.4, < 2.0.9.4>= 2.1.0, < 2.1.4.4>= 2.2.0, < 2.2.8.1
Debian LinuxOperating system
Affected:= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.9.4 / 2.1.4.4 / 2.2.8.1 or later
Fixed in 2.0.9.42.1.4.42.2.8.1
Vendor patch github.com →
Recommended fix High confidence

Rack 2.0.9.4, 2.1.4.4, 2.2.8.1, or 3.0.9.1 depending on your current major version branch

  1. Identify the current Rack gem version in your project (check Gemfile.lock)
  2. Determine which upgrade path applies based on your current major version: for Rack 2.0.x upgrade to 2.0.9.4, for 2.1.x upgrade to 2.1.4.4, for 2.2.x upgrade to 2.2.8.1, for 3.0.x upgrade to 3.0.9.1
  3. Update the Gemfile with the appropriate fixed version (e.g., gem 'rack', '~> 2.2.8')
  4. Run bundle update rack to apply the fix
  5. Alternatively, if upgrading Rack is not feasible, upgrade Ruby to version 3.2 or newer which has built-in mitigations for this vulnerability
  6. Restart the application to ensure the new Rack version is loaded
Caveat Review the Rack changelog for the version you are upgrading to for any breaking changes between your current version and the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26146 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data