CVE-2026-126085: Active Storage: Possible circumvention of file size limits in Active Storage direct uploads to Google Cloud Storage
Impact ActiveStorage::Service::GCSService#urlfordirectupload does not bind the declared content length into the signed direct-upload URL, and #headersfordirectupload returns no length constraint, so the URL authorizes an upload body of any size.
Published Nov 10, 2026
Affected packages
activestorage
- Ecosystem
- RubyGems
- Affected
- >= 8.1.0.beta1, < 8.1.4.1
- Fixed in
- 8.1.4.1
- Check
bundle info activestorage
activestorage
- Ecosystem
- RubyGems
- Affected
- < 8.0.5.2
- Fixed in
- 8.0.5.2
- Check
bundle info activestorage
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
- https://github.com/rails/rails/security/advisories/GHSA-hfr4-8rjc-97m2
- https://github.com/rails/rails/commit/7fe85a72a789eae5ee070ce3ee1dad10a8a5f70c
- https://github.com/rails/rails/commit/e19916cea31cbfb0030b165ae853b741f8dd57a7
- https://github.com/rails/rails/releases/tag/v8.0.5.2
- https://github.com/rails/rails/releases/tag/v8.1.4.1
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/activestorage/GHSA-hfr4-8rjc-97m2.yml
- https://github.com/advisories/GHSA-hfr4-8rjc-97m2
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesCVE-2026-122006
Active Storage: Possible arbitrary file write and read in image analysis
critical9.8Nov 12, 2026CVE-2026-126084
Active Storage: Unsigned Content-Type in GCS direct uploads with cache_control
medium4.7Nov 12, 2026CVE-2026-126188
Active Storage: Possible local file disclosure in video previews and analysis
low3.7Nov 12, 2026CVE-2026-126071
Active Storage: Possible DoS vulnerability in Active Storage proxy mode via storage errors during streaming
medium5.3Nov 10, 2026CVE-2026-126074
Active Storage: Possible DoS vulnerability in Active Storage filename handling
medium4.3Nov 10, 2026CVE-2026-126186
Active Storage: Possible arbitrary file read and remote code execution in video previews, analysis and image processing
high8.8Nov 10, 2026
