MediumGHSA-8h22-8cf7-hq6gBIT-rails-2024-26144CVE-2024-26144

Rails has possible Sensitive Session Information Leak in Active Storage

Published 27 Feb 2024 · Updated 10 Sept 2026

Is your project on an affected activestorage?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=5.2.0 <6.1.7.7
Fixed in
6.1.7.7
Update to the fixed version for your release line, for example:bundle update --conservative activestorage # Gemfile: '>= 6.1.7.7'
Affected
>=7.0.0 <7.0.8.1
Fixed in
7.0.8.1
Update to the fixed version for your release line, for example:bundle update --conservative activestorage # Gemfile: '>= 7.0.8.1'

Details

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!

Is GHSA-8h22-8cf7-hq6g in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected activestorage, and gives you the command that fixes it.

More advisories for activestorage

  • CriticalCVE-2026-122006Active Storage: Possible arbitrary file write and read in image analysis · 12 Nov 2026
  • MediumCVE-2026-126084Active Storage: Unsigned Content-Type in GCS direct uploads with cache_control · 12 Nov 2026
  • LowCVE-2026-126188Active Storage: Possible local file disclosure in video previews and analysis · 12 Nov 2026
  • HighCVE-2026-126186Active Storage: Possible arbitrary file read and remote code execution in video previews, analysis and image processing · 10 Nov 2026
  • MediumCVE-2026-126085Active Storage: Possible circumvention of file size limits in Active Storage direct uploads to Google Cloud Storage · 10 Nov 2026
  • MediumCVE-2026-126074Active Storage: Possible DoS vulnerability in Active Storage filename handling · 10 Nov 2026
All 18 advisories for activestorage

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.