What is CVE-2022-44570?

CVE-2022-44570 is a high-severity uncontrolled resource consumption vulnerability in rack (rubygems), affecting versions >= 1.5.0, < 2.0.9.2. It is fixed in 2.0.9.2, 2.1.4.2, 2.2.6.2, 3.0.4.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is CVE-2022-44570?

CVE-2022-44570 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of rack are affected by CVE-2022-44570?

rack (rubygems) versions >= 1.5.0, < 2.0.9.2 is affected.

Is there a fix for CVE-2022-44570?

Yes. CVE-2022-44570 is fixed in 2.0.9.2, 2.1.4.2, 2.2.6.2, 3.0.4.1. Upgrade to this version or later.

Is CVE-2022-44570 exploitable, and should I be worried?

Whether CVE-2022-44570 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-44570 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2022-44570 in rack | Intelligent Application Security

Q: How severe is CVE-2022-44570?

CVE-2022-44570 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of rack are affected by CVE-2022-44570?

rack (rubygems) versions >= 1.5.0, < 2.0.9.2 is affected.

Q: Is there a fix for CVE-2022-44570?

Yes. CVE-2022-44570 is fixed in 2.0.9.2, 2.1.4.2, 2.2.6.2, 3.0.4.1. Upgrade to this version or later.

Q: Is CVE-2022-44570 exploitable, and should I be worried?

Whether CVE-2022-44570 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-44570 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-44570?

Upgrade: rack to 2.0.9.2 or later, rack to 2.1.4.2 or later, rack to 2.2.6.2 or later, rack to 3.0.4.1 or later.

Summary

There is a possible denial of service vulnerability in the Range header parsing component of Rack. This vulnerability has been assigned the CVE identifier CVE-2022-44570.

Versions Affected: >= 1.5.0 Not affected: None. Fixed Versions: 2.0.9.2, 2.1.4.2, 2.2.6.2, 3.0.0.1
Impact

Carefully crafted input can cause the Range header parsing component in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that deal with Range requests (such as streaming applications, or applications that serve files) may be impacted.
Releases

The fixed releases are available at the normal locations.
Workarounds

There are no feasible workarounds for this issue.
Patches

To aid users who aren’t able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.

2-0-Fix-ReDoS-in-Rack-Utils.get_byte_ranges.patch - Patch for 2.0 series
2-1-Fix-ReDoS-in-Rack-Utils.get_byte_ranges.patch - Patch for 2.1 series
2-2-Fix-ReDoS-in-Rack-Utils.get_byte_ranges.patch - Patch for 2.2 series
3-0-Fix-ReDoS-in-Rack-Utils.get_byte_ranges.patch - Patch for 3.0 series

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2022-44570 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.9.2, 2.1.4.2, 2.2.6.2, 3.0.4.1); upgrading removes the vulnerable code path.

Affected versions

rack (>= 1.5.0, < 2.0.9.2) rack (>= 2.1.0.0, < 2.1.4.2) rack (>= 2.2.0.0, < 2.2.6.2) rack (>= 3.0.0.0, < 3.0.4.1)

Security releases

rack → 2.0.9.2 (rubygems) rack → 2.1.4.2 (rubygems) rack → 2.2.6.2 (rubygems) rack → 3.0.4.1 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

rack to 2.0.9.2 or later; rack to 2.1.4.2 or later; rack to 2.2.6.2 or later; rack to 3.0.4.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-44570? CVE-2022-44570 is a high-severity uncontrolled resource consumption vulnerability in rack (rubygems), affecting versions >= 1.5.0, < 2.0.9.2. It is fixed in 2.0.9.2, 2.1.4.2, 2.2.6.2, 3.0.4.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is CVE-2022-44570? CVE-2022-44570 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of rack are affected by CVE-2022-44570? rack (rubygems) versions >= 1.5.0, < 2.0.9.2 is affected.
Is there a fix for CVE-2022-44570? Yes. CVE-2022-44570 is fixed in 2.0.9.2, 2.1.4.2, 2.2.6.2, 3.0.4.1. Upgrade to this version or later.
Is CVE-2022-44570 exploitable, and should I be worried? Whether CVE-2022-44570 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-44570 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-44570?
- Upgrade rack to 2.0.9.2 or later
- Upgrade rack to 2.1.4.2 or later
- Upgrade rack to 2.2.6.2 or later
- Upgrade rack to 3.0.4.1 or later

Other vulnerabilities in rack

CVE-IDSeverityPackage summary

CVE-2026-34835Mediumrack: Rack::Request accepts invalid Host characters, enabling host allowlist bypass CVE-2026-34831Mediumrack: Rack has Content-Length mismatch in Rack::Files error responses CVE-2026-34830Mediumrack: Rack::Sendfile header-based X-Accel-Mapping regex injection enables unauthorized X-Accel-Redirect CVE-2026-34829Highrack: Rack's multipart parsing without Content-Length header allows unbounded chunked file uploads CVE-2026-34763Mediumrack: Rack has a root directory disclosure via unescaped regex interpolation in Rack::Directory