# CVE-2024-26144: Possible Sensitive Session Information Leak in Active Storage

> Attackers can leak sensitive session information via cached Set-Cookie headers in Active Storage blob responses, affecting Ruby on Rails applications.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Feb 2024
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-rails-2024-26144, DEBIAN-CVE-2024-26144, GHSA-8h22-8cf7-hq6g, OESA-2024-1364, OESA-2024-1365, OESA-2024-1366, OESA-2024-1367, UBUNTU-CVE-2024-26144

## What is CVE-2024-26144?

CVE-2024-26144 is a medium-severity vulnerability in Rubyonrails Rails, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rails is a web-application framework. Starting with version 5.2.0, 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. The vulnerability is fixed in 7.0.8.1 and 6.1.7.7.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-26144?

5 open source packages ship an affected version, including rails and activestorage. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rails` | Bitnami | From 5.2.0 | 6.1.8, 7.0.9 |
| `activestorage` | RubyGems | From 5.2.0 | 6.1.7.7 |
| `activestorage` | RubyGems | From 5.2.0 | 6.1.7.7 |
| `activestorage` | RubyGems | From 7.0.0 | 7.0.8.1 |
| `activestorage` | RubyGems | From 7.0.0 | 7.0.8.1 |

Products: Rubyonrails Rails.

## How do I fix CVE-2024-26144?

Upgrade rails to a fixed version for your release line: 6.1.8 or 7.0.9.

## Is CVE-2024-26144 being exploited?

There is no known exploitation of CVE-2024-26144 in the wild and no public exploit code.

Public exploit code:

- Known security vulnerabilities detected. CVE-2022-21831 Critical severity CVE-2025-24293 Critical severity CVE-2020-8162 High severity CVE-2024-26144 Moderate severity (github_poc): https://github.com/usutani/study-turbolinks-link
- https://github.com/gmo-ierae/CVE-2024-26144-test (github_poc): https://github.com/gmo-ierae/CVE-2024-26144-test

## Other vulnerabilities in Rubyonrails Rails

- [CVE-2013-0277](https://insights.sbomify.com/CVE-2013-0277/): Active Record contains deserialization of arbitrary YAML (critical 10.0)
- [CVE-2017-17916](https://insights.sbomify.com/CVE-2017-17916/): SQL injection in n/a (high 8.1)
- [CVE-2017-17917](https://insights.sbomify.com/CVE-2017-17917/): SQL injection in n/a (high 8.1)
- [CVE-2026-33195](https://insights.sbomify.com/CVE-2026-33195/): Rails Active Storage has possible Path Traversal in DiskService (high 8.0)
- [CVE-2024-26142](https://insights.sbomify.com/CVE-2024-26142/): Rails possible ReDoS vulnerability in Accept header parsing in Action Dispatch (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26144 and fix it if it is affected.

What it is: CVE-2024-26144 is a medium-severity vulnerability in Rubyonrails Rails, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-26144 in the wild and no public exploit code.

Affected packages and fixed versions:
- rails (Bitnami): affected from 5.2.0; fixed in 6.1.8, 7.0.9
- activestorage (RubyGems): affected from 5.2.0; fixed in 6.1.7.7
- activestorage (RubyGems): affected from 5.2.0; fixed in 6.1.7.7
- activestorage (RubyGems): affected from 7.0.0; fixed in 7.0.8.1
- activestorage (RubyGems): affected from 7.0.0; fixed in 7.0.8.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26144/ (Markdown: https://insights.sbomify.com/CVE-2024-26144/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26144
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26144
- OSV: https://osv.dev/vulnerability/CVE-2024-26144

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26144/
Summaries are generated and may contain mistakes; the official description above is the record.