CVE-2024-26144

CVE-2024-26144 is a medium-severity security vulnerability in activestorage (rubygems), affecting versions >= 5.2.0, < 6.1.7.7. It is fixed in 6.1.7.7, 7.0.8.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Rails has possible Sensitive Session Information Leak in Active Storage

Possible Sensitive Session Information Leak in Active Storage

There is a possible sensitive session information leak in Active Storage. By
default, Active Storage sends a Set-Cookie header along with the user's
session cookie when serving blobs. It also sets Cache-Control to public.
Certain proxies may cache the Set-Cookie, leading to an information leak.

This vulnerability has been assigned the CVE identifier CVE-2024-26144.

Versions Affected: >= 5.2.0, < 7.1.0
Not affected: < 5.2.0, > 7.1.0
Fixed Versions: 7.0.8.1, 6.1.7.7

Impact

A proxy which chooses to caches this request can cause users to share
sessions. This may include a user receiving an attacker's session or vice
versa.

This was patched in 7.1.0 but not previously identified as a security
vulnerability.

All users running an affected release should either upgrade or use one of the
workarounds immediately.

Releases

The fixed releases are available at the normal locations.

Workarounds

Upgrade to Rails 7.1.X, or configure caching proxies not to cache the
Set-Cookie headers.

Credits

Thanks to tyage for reporting this!

Impact

CVE-2024-26144 has a CVSS score of 5.3 (Medium). 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 (6.1.7.7, 7.0.8.1); upgrading removes the vulnerable code path.

Affected versions

activestorage (>= 5.2.0, < 6.1.7.7) activestorage (>= 7.0.0, < 7.0.8.1)

Security releases

activestorage → 6.1.7.7 (rubygems) activestorage → 7.0.8.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.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

activestorage to 6.1.7.7 or later; activestorage to 7.0.8.1 or later

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

Frequently Asked Questions

  1. What is CVE-2024-26144? CVE-2024-26144 is a medium-severity security vulnerability in activestorage (rubygems), affecting versions >= 5.2.0, < 6.1.7.7. It is fixed in 6.1.7.7, 7.0.8.1.
  2. How severe is CVE-2024-26144? CVE-2024-26144 has a CVSS score of 5.3 (Medium). 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.
  3. Which versions of activestorage are affected by CVE-2024-26144? activestorage (rubygems) versions >= 5.2.0, < 6.1.7.7 is affected.
  4. Is there a fix for CVE-2024-26144? Yes. CVE-2024-26144 is fixed in 6.1.7.7, 7.0.8.1. Upgrade to this version or later.
  5. Is CVE-2024-26144 exploitable, and should I be worried? Whether CVE-2024-26144 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
  6. What actually determines whether CVE-2024-26144 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.
  7. How do I fix CVE-2024-26144?
    • Upgrade activestorage to 6.1.7.7 or later
    • Upgrade activestorage to 7.0.8.1 or later

Other vulnerabilities in activestorage

CVE-IDSeverityPackage summary
CVE-2026-33658Lowactivestorage: Rails Active Storage has a possible DoS vulnerability in proxy mode via multi-range requestsCVE-2026-33202Mediumactivestorage: Rails Active Storage has possible glob injection in its DiskServiceCVE-2026-33195Highactivestorage: Rails Active Storage has possible Path Traversal in DiskServiceCVE-2026-33174Mediumactivestorage: Rails Active Storage has a possible DoS vulnerability when in proxy mode via Range requestsCVE-2026-33173Mediumactivestorage: Rails Active Storage has possible content type bypass via metadata in direct uploads

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo