rails activestorage prior 7.2.3.1/8.0.4.1/8.1.2.1 DirectUploadsController intent by broadcast receiver
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in rails activestorage. Affected by this vulnerability is the function DirectUploadsController. This manipulation causes intent by broadcast receiver.
This vulnerability is tracked as CVE-2026-33173. The attack is possible to be carried out remotely. No exploit exists.
You should upgrade the affected component.
Details
A vulnerability was found in rails activestorage. It has been declared as problematic. Affected by this vulnerability is the function DirectUploadsController. The manipulation with an unknown input leads to a intent by broadcast receiver vulnerability. The CWE definition for the vulnerability is CWE-925. The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source. As an impact it is known to affect integrity. The summary by CVE is:
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, `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 direct-upload client can set these flags to skip MIME detection and analysis. This allows an attacker to upload arbitrary content while claiming a safe `content_type`, bypassing any validations that rely on Active Storage's automatic content type identification. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-33173 since 03/17/2026. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 7.2.3.1, 8.0.4.1 or 8.1.2.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 707c0f1f41f067fdf96d54e99d43b28dfaae7e53 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Intent by broadcast receiverCWE: CWE-925
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: activestorage 7.2.3.1/8.0.4.1/8.1.2.1
Patch: 707c0f1f41f067fdf96d54e99d43b28dfaae7e53
Timeline
03/17/2026 CVE reserved03/24/2026 Advisory disclosed
03/24/2026 VulDB entry created
03/28/2026 VulDB entry last update
Sources
Advisory: GHSA-qcfx-2mfw-w4cgStatus: Confirmed
CVE: CVE-2026-33173 (🔒)
GCVE (CVE): GCVE-0-2026-33173
GCVE (VulDB): GCVE-100-352627
Entry
Created: 03/24/2026 02:47Updated: 03/28/2026 08:16
Changes: 03/24/2026 02:47 (69), 03/28/2026 08:16 (12)
Complete: 🔍
Cache ID: 216:4AC:103
No comments yet. Languages: en.
Please log in to comment.