activestorage · Active Storage: Possible circumvention of file size limits in Active Storage direct uploads to Google Cloud Storage
Affects activestorageSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.3 Medium : upgrade to 8.1.4.1 when convenient.
Data as of 10 Nov 2026, 22:36 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 8.1.4.1, 8.0.5.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade activestorage to 8.1.4.1; activestorage to 8.0.5.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RubyGemsactivestorage | Affected
| Fixed in
|
| RubyGemsactivestorage | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Active Storage versions 8.1.4.1 or 8.0.5.2 or later where the issue is fixed. For those unable to upgrade immediately, apply the provided patches for versions 8.1 and 8.0. Additionally, update the Google Cloud Storage bucket CORS configuration to include 'x-goog-content-length-range' in the 'responseHeader' list to ensure browser direct uploads function correctly after the upgrade. No other mitigation is required as the fix enforces size constraints server-side.
Description
Active Storage's Google Cloud Storage direct upload feature did not enforce file size limits properly, allowing clients to upload files larger than the declared size. This could bypass application-level file size validations and quotas. The issue was fixed by signing an 'x-goog-content-length-range' header that enforces the declared size, with fixed versions released.
References
- github.com/rails/rails/security/advisories/GHSA-hfr4-8rjc-97m2 (opens in a new tab)
- github.com/rails/rails/commit/7fe85a72a789eae5ee070ce3ee1dad10a8a5f70c (opens in a new tab)
- github.com/rails/rails/commit/e19916cea31cbfb0030b165ae853b741f8dd57a7 (opens in a new tab)
- github.com/rails/rails (opens in a new tab)
- github.com/rails/rails/releases/tag/v8.0.5.2 (opens in a new tab)
- github.com/rails/rails/releases/tag/v8.1.4.1 (opens in a new tab)
- github.com/rubysec/ruby-advisory-db/blob/master/gems/activestorage/GHSA-hfr4-8rjc-97m2.yml (opens in a new tab)