CVE-2026-33202 in the critical feed json
Rails Active Storage has possible glob injection in its DiskService
published 2026-03-23 7 mo ago modified 2026-09-10 59 d ago also EUVD-2026-14634 , GHSA-73f9-jhhh-hr5m
- cvss
- 9.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
Active Storage allows users to attach cloud and local files in Rails applications. Prior to versions 8.1.2.1, 8.0.4.1, and 7.2.3.1, Active Storage's `DiskService#delete_prefixed` passes blob keys directly to `Dir.glob` without escaping glob metacharacters. If a blob key contains attacker-controlled input or custom-generated keys with glob metacharacters, it may be possible to delete unintended files from the storage directory. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch.
Patch / fix
- rubygems activestorage 7.2.3.1, 8.0.4.1, 8.1.2.1
- rubyonrails rails 7.2.3.1, 8.0.4.1, 8.1.2.1
- rails Debian 12 2:6.1.7.10+dfsg-1~deb12u3
- rails Debian 13 2:7.2.2.2+dfsg-2~deb13u2
- rails Debian 14 2:7.2.3.1+dfsg-1
debian advisories DEBIAN-CVE-2026-33202
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-33202 updated cvss 6.5
rails: Active Storage: Unintended file deletion via crafted blob keys
-
Red Hat 3scale API Management Platform 2 3scale-amp21/zync, 3scale-amp22/zync, 3scale-amp24/zync, 3scale-amp25/zync, 3scale-amp26/zync, 3scale-amp20/system, +9 moreaffected: workaround, no fix planned “Will not fix”
-
Red Hat 3scale API Management Platform 2 3scale-amp2/zync-rhel9, 3scale-amp2/system-rhel9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.6 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U |
| CNA | 4.0 | 6.6 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | activestorage | >=8.1.0.beta1, <8.1.2.1 >=8.0.0.beta1, <8.0.4.1 <7.2.3.1 |
8.1.2.1 8.0.4.1 7.2.3.1 |
Affected products
- rails activestorage
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
- Technology feeds
References
-
github.com
/rails/rails/commit/8c9676b803820110548cdb7523800db43bc6874c
web, patch
-
github.com
/rails/rails/commit/955284d26e469a9c026a4eee5b21f0414ab0bccf
web, patch
-
github.com
/rails/rails/commit/fa19073546360856e9f4dab221fc2c5d73a45e82
web, patch
-
github.com
/rails/rails/security/advisories/GHSA-73f9-jhhh-hr5m
web, vendor-advisory, advisory
-
github.com
/rails/rails/releases/tag/v7.2.3.1
web, release-notes
-
github.com
/rails/rails/releases/tag/v8.0.4.1
web, release-notes
-
github.com
/rails/rails/releases/tag/v8.1.2.1
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-33202
advisory
-
github.com
/rails/rails
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/activestorage/CVE-2026-33202.yml
web
Sources
- CVE List CVE-2026-33202
- GitHub Advisory GHSA-73f9-jhhh-hr5m
- NVD CVE-2026-33202
- Maintainer advisory GHSA-73f9-jhhh-hr5m
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of rails/rails published their own advisory on GitHub. Reviewed sources take precedence over it.