GHSA-qcfx-2mfw-w4cgMedium
Rails Active Storage has possible content type bypass via metadata in direct uploads
🔗 CVE IDs covered (1)
📋 Description
Impact
Active Storage's DirectUploadsController accepts arbitrary metadata from the client and persists it on the blob. Because internal flags like identified and analyzed are stored in the same metadata hash, a malicious direct-upload client could set these flags.
Releases
The fixed releases are available at the normal locations.
Credit
This was responsible reported by Hackerone researcher pwnie
🎯 Affected products3
- rubygems/activestorage:>= 8.1.0.beta1, < 8.1.2.1
- rubygems/activestorage:>= 8.0.0.beta1, < 8.0.4.1
- rubygems/activestorage:< 7.2.3.1
🔗 References (10)
- https://github.com/rails/rails/security/advisories/GHSA-qcfx-2mfw-w4cg
- https://github.com/rails/rails/commit/707c0f1f41f067fdf96d54e99d43b28dfaae7e53
- https://github.com/rails/rails/commit/8fcb934caadc79c8cc4ce53287046d0f67005b3e
- https://github.com/rails/rails/commit/d9502f5214e2198245a4c1defe9cd02a7c8057d0
- https://github.com/rails/rails/releases/tag/v7.2.3.1
- https://github.com/rails/rails/releases/tag/v8.0.4.1
- https://github.com/rails/rails/releases/tag/v8.1.2.1
- https://nvd.nist.gov/vuln/detail/CVE-2026-33173
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/activestorage/CVE-2026-33173.yml
- https://github.com/advisories/GHSA-qcfx-2mfw-w4cg