What is CVE-2015-3225?

CVE-2015-3225 is a medium-severity security vulnerability in rack (rubygems), affecting versions >= 1.6.0, < 1.6.2. It is fixed in 1.6.2, 1.5.4, 1.4.6.

Which versions of rack are affected by CVE-2015-3225?

rack (rubygems) versions >= 1.6.0, < 1.6.2 is affected.

Is there a fix for CVE-2015-3225?

Yes. CVE-2015-3225 is fixed in 1.6.2, 1.5.4, 1.4.6. Upgrade to this version or later.

Is CVE-2015-3225 exploitable, and should I be worried?

Whether CVE-2015-3225 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-2015-3225 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-2015-3225 in rack | Intelligent Application Security

Q: Which versions of rack are affected by CVE-2015-3225?

rack (rubygems) versions >= 1.6.0, < 1.6.2 is affected.

Q: Is there a fix for CVE-2015-3225?

Yes. CVE-2015-3225 is fixed in 1.6.2, 1.5.4, 1.4.6. Upgrade to this version or later.

Q: Is CVE-2015-3225 exploitable, and should I be worried?

Whether CVE-2015-3225 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-2015-3225 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-2015-3225?

Upgrade: rack to 1.6.2 or later, rack to 1.5.4 or later, rack to 1.4.6 or later.

Summary

lib/rack/utils.rb in Rack before 1.5.4 and 1.6.x before 1.6.2, as used with Ruby on Rails 3.x and 4.x and other products, allows remote attackers to cause a denial of service (SystemStackError) via a request with a large parameter depth.

Impact

Affected versions

rack (>= 1.6.0, < 1.6.2) rack (>= 1.5.0, < 1.5.4) rack (>= 1.4.0, < 1.4.6)

Security releases

rack → 1.6.2 (rubygems) rack → 1.5.4 (rubygems) rack → 1.4.6 (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 1.6.2 or later; rack to 1.5.4 or later; rack to 1.4.6 or later

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

Frequently Asked Questions

What is CVE-2015-3225? CVE-2015-3225 is a medium-severity security vulnerability in rack (rubygems), affecting versions >= 1.6.0, < 1.6.2. It is fixed in 1.6.2, 1.5.4, 1.4.6.
Which versions of rack are affected by CVE-2015-3225? rack (rubygems) versions >= 1.6.0, < 1.6.2 is affected.
Is there a fix for CVE-2015-3225? Yes. CVE-2015-3225 is fixed in 1.6.2, 1.5.4, 1.4.6. Upgrade to this version or later.
Is CVE-2015-3225 exploitable, and should I be worried? Whether CVE-2015-3225 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-2015-3225 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-2015-3225?
- Upgrade rack to 1.6.2 or later
- Upgrade rack to 1.5.4 or later
- Upgrade rack to 1.4.6 or later

Other vulnerabilities in rack

CVE-2026-34835 CVE-2026-34831 CVE-2026-34829 CVE-2026-34763 CVE-2026-34230