MediumGHSA-hfr4-8rjc-97m2CVE-2026-126085

Active Storage: Possible circumvention of file size limits in Active Storage direct uploads to Google Cloud Storage

Published 10 Nov 2026 · Updated 10 Nov 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
>=8.1.0.beta1 <8.1.4.1
Fixed in
8.1.4.1
Update to the fixed version for your release line, for example:bundle update --conservative activestorage # Gemfile: '>= 8.1.4.1'
Affected
<8.0.5.2
Fixed in
8.0.5.2
Update to the fixed version for your release line, for example:bundle update --conservative activestorage # Gemfile: '>= 8.0.5.2'

Details

Impact

ActiveStorage::Service::GCSService#url_for_direct_upload does not bind the declared content length into the signed direct-upload URL, and #headers_for_direct_upload returns no length constraint, so the URL authorizes an upload body of any size. A direct-upload client could store a file larger than the byte_size it declared, and the resulting blob keeps the declared size, possibly bypassing application file size validations and quotas. This is the weakness that CVE-2020-8162 fixed in the S3 service.

Applications that store files in Google Cloud Storage and accept direct uploads are affected.

Details

The fixed releases sign an x-goog-content-length-range header that matches the blob's declared byte_size and return it from headers_for_direct_upload, so Cloud Storage rejects an upload body of any other size. Browsers send this header with the direct upload, so a bucket's CORS configuration must list x-goog-content-length-range in responseHeader, or browser direct uploads fail after the upgrade. The Active Storage CHANGELOG and the CORS example in the Active Storage guide show the change.

Releases

The fixed releases are available at the normal locations.

Patches for those who cannot upgrade at once:

  • 8.1: https://github.com/rails/rails/commit/e19916cea31cbfb0030b165ae853b741f8dd57a7.patch
  • 8.0: https://github.com/rails/rails/commit/7fe85a72a789eae5ee070ce3ee1dad10a8a5f70c.patch

Credit

This issue was responsibly reported by HackerOne researcher f4cts.

Is GHSA-hfr4-8rjc-97m2 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-126074Active Storage: Possible DoS vulnerability in Active Storage filename handling · 10 Nov 2026
  • MediumCVE-2026-126071Active Storage: Possible DoS vulnerability in Active Storage proxy mode via storage errors during streaming · 10 Nov 2026
All 18 advisories for activestorage

References

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