rails · Ruby on Rails · published 2026-11-10
CVE-2026-126084Active Storage: Unsigned Content-Type in Active Storage GCS direct uploads with cache_control
Routine No exploitation evidence; EPSS 0.1%.
CVE-2026-126084 is not known to be exploited in the wild. EPSS estimates a 0.1% chance of exploitation in the next 30 days, higher than 3% of all CVEs. This Ruby on Rails vulnerability: CVSS 4.7 (v3.1). Fixed upstream in Ruby on Rails 8.1.4.1, 8.0.5.2; Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Ruby on Rails 8.1.4.1, 8.0.5.2.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | rails | No fix yet |
| 12 bookworm | rails | No fix yet | |
| Ubuntu | 26.04 LTS | rails | No fix yet |
| 24.04 LTS | rails | No fix yet |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Web frameworkRuby on Rails
Ruby on Rails security releases: 8.1.4.1, 8.0.5.2
Upgrade to
8.1.4.18.0.5.2Why: Vendor security release for server software (most severe: CVE-2026-126186).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.1% (3th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 4.7 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- rails rails
>= 8.1, < 8.1.4.1(affected)< 8.0.5.2(affected)
Description (from the CVE record)#
Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, when a GCS service is configured with the cache_control option, ActiveStorage::Service::GCSService#url_for_direct_upload signs direct-upload URLs with V4, and the V4 signature covers only the Cache-Control and Host headers. A direct-upload client can therefore send a Content-Type of its choosing, and can omit the declared Content-MD5, without invalidating the URL. GCS stores the supplied content type as object metadata, which takes precedence over the response-content-type that Active Storage sets on download URLs, so an uploaded object could be served as inline HTML under the application's bucket path on storage.googleapis.com. Script in such an object runs on the storage origin rather than the application's, but could register a Service Worker scoped to the bucket path and read or replace a victim's later responses for signed URLs in that bucket. Applications that use the GCS service with cache_control configured and accept direct uploads are affected. GCS services without cache_control sign with V2 and are not affected. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.
Quoted from the CVE Program record.