CVE-2026-33195: Rails Active Storage has possible Path Traversal in DiskService
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#path_for` does not validate that the resolved filesystem path remains within the storage root directory. If a blob key containing path traversal sequences (e.g. `../`) is used, it could allow reading, writing, or deleting arbitrary files on the server. Blob keys are expected to be trusted strings, but some applications could be passing user input as keys and would be affected. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch.
Security readout for executives and security teams
Plain-English summary
This flaw affects Rails applications using Active Storage with local disk storage. In vulnerable versions, a crafted blob key could escape the intended storage directory and touch other server files. The most exposed applications are those that let users influence blob keys, which Rails normally expects to be trusted internal values.
Executive priority
Patch during the next urgent security maintenance window, sooner for upload-heavy or externally exposed Rails systems. The business risk is unauthorized access to server files, but not every Rails app is automatically exploitable.
Technical view
Active Storage DiskService#path_for did not validate that resolved paths stayed under the configured storage root. If application code passed untrusted input into blob keys, path traversal could permit arbitrary file read, write, or delete on the server. Rails patched this in 7.2.3.1, 8.0.4.1, and 8.1.2.1.
Likely exposure
Rails applications using Active Storage DiskService before 7.2.3.1, 8.0.4.1, or 8.1.2.1. Exposure is highest where application logic accepts or derives blob keys from user-controlled input.
Exploitation context
The bundle does not show KEV listing or cited evidence of active exploitation. Exploitation appears application-dependent because blob keys are expected to be trusted; vulnerable behavior requires a path-traversal-capable key to reach DiskService#path_for.
Researcher notes
The advisory says blob keys are expected to be trusted, so impact hinges on app-specific key handling. CVSS is 8.1 with network attack vector, high privileges, and user interaction. Review patch commits for containment logic, but avoid assuming all Active Storage deployments are reachable.
Mitigation direction
Upgrade Rails/Active Storage to 7.2.3.1, 8.0.4.1, or 8.1.2.1.
Prioritize internet-facing Rails apps that accept uploads or manage local attachments.
Audit custom code that sets blob keys from request parameters or user-controlled data.
Treat blob keys as internal trusted identifiers, not user-supplied filenames.
Check Red Hat or distribution guidance if using packaged Rails components.
Validation and detection
Inventory Rails and activestorage versions in Gemfile.lock, SBOMs, and deployed images.
Confirm affected version ranges are absent from production and staging.
Review Active Storage configuration for DiskService or local disk use.
Inspect custom upload paths for user-controlled blob key assignment.
Verify dependency scanners identify CVE-2026-33195 after package metadata refresh.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
11Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.