p PatchFirst

PatchFirst · Latest vulnerabilities

activestorage vulnerabilities

Vulnerabilities published for activestorage in the last 30 days: 7. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 18

  1. CVE-2026-126188

    Low · CVSS 3.7EPSS 0.28%Fix available

    Active Storage: Possible local file disclosure in Active Storage video previews and analysis

    Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.0.5.2 and from 8.1 until 8.1.4.1, Active Storage's ActiveStorage::Previewer::VideoPreviewer, ActiveStorage::Analyzer::VideoAnalyzer, and ActiveStorage::Analyzer::AudioAnalyzer pass uploaded blob contents to FFmpeg without restricting the demuxer. A direct upload can retain a client-declared video/* or audio/* content type for an HLS playlist. FFmpeg content probing selects the hls demuxer, which opens attacker-named file:// segments when the blob is previewed or analyzed. Applications that accept untrusted

    • Update to 8.0.5.2
    • Update to 8.1.4.1
    Published Updated
  2. CVE-2026-126186

    High · CVSS 8.8EPSS 0.51%Fix available

    Active Storage: Possible arbitrary file read and remote code execution in Active Storage video previews, analysis and image processing

    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, ActiveStorage::Blob#open writes a blob to a tempfile whose name carries the extension of the uploaded filename, and hands that path to ffprobe (VideoAnalyzer, AudioAnalyzer), ffmpeg (VideoPreviewer) and ImageMagick (ImageAnalyzer, the :mini_magick variant processor). These tools select a decoder from the file extension when the content does not identify its own format, so an attacker who chooses the filename and declares the content type of an upload chooses which decoder processes it. A

    • Update to 8.0.5.2
    • Update to 8.1.4.1
    Published Updated
  3. CVE-2026-126085

    Medium · CVSS 5.3EPSS 0.48%Fix available

    Active Storage: Possible circumvention of file size limits in Active Storage direct uploads to Google Cloud Storage

    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, ActiveStorage::Service::GCSService#url_for_direct_upload does not bind the declared content length into the signed direct-upload URL, and #headers_for_direct_upload returns no length constraint, so the URL authorizes an upload body of any size. A direct-upload client could store a file larger than the byte_size it declared, and the resulting blob keeps the declared size, possibly bypassing application file size validations and quotas. This is the weakness that CVE-2020-8162 fixed in the

    • Update to 8.0.5.2
    • Update to 8.1.4.1
    Published Updated
  4. CVE-2026-126084

    Medium · CVSS 4.7EPSS 0.14%Fix available

    Active Storage: Unsigned Content-Type in Active Storage GCS direct uploads with cache_control

    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 St

    • Update to 8.0.5.2
    • Update to 8.1.4.1
    Published Updated
  5. CVE-2026-126074

    Medium · CVSS 4.3EPSS 0.5%Fix available

    Active Storage: Possible DoS vulnerability in Active Storage filename handling

    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, ActiveStorage::Filename#base and #extension_with_delimiter, and therefore #extension, pass the stored filename unmodified to File.basename and File.extname, which raise ArgumentError when the name contains a NUL byte. Active Storage stores the client-supplied filename verbatim, so a user who is permitted to upload an attachment could persist such a filename on databases that accept NUL bytes in string columns, such as SQLite and MySQL/MariaDB. Each subsequent request that builds a varian

    • Update to 8.0.5.2
    • Update to 8.1.4.1
    Published Updated
  6. CVE-2026-126071

    Medium · CVSS 5.3EPSS 0.44%Fix available

    Active Storage: Possible DoS vulnerability in Active Storage proxy mode via storage errors during streaming

    Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. From 8.0 until 8.0.5.2 and 8.1.4.1, when Active Storage serves a file through its proxy controllers, ActiveStorage::Streaming#send_blob_stream handles an error from the storage service by calling head to send a 404 or 500 response. If the error occurs after the first chunk has been written, the response is already committed, and head replaces the response body while the server is still reading the original ActionController::Live buffer. That buffer is never closed, so the server thread handling the request blocks unt

    • Update to 8.0.5.2
    • Update to 8.1.4.1
    Published Updated
  7. CVE-2026-122006

    Critical · CVSS 9.8EPSS 0.73%Public exploitFix available

    CVE-2026-122006

    The activestorage gem before 8.1.4.1 for Ruby on Rails, when ImageMagick attachment processing occurs, can allow server read and write operations (e.g., reading secret_key_base) because the ImageMagick analyzer runs when a file is attached, and there is not an ImageMagick security policy to block unintended functionality.

    • Update to 8.0.5.2
    • Update to 8.1.4.1
    Published Updated
  8. CVE-2026-66066

    Critical · CVSS 9.5EPSS 32.9%Public exploitFix available

    Action Pack: Possible arbitrary file read and remote code execution in Active Storage variant processing

    Action Pack is a framework for handling and responding to web requests. In versions prior to 7.2.3.2, 8.0.5.1 and 8.1.3.1, Active Storage does not disable libvips operations marked unsafe for untrusted content, allowing a crafted upload to invoke such an operation. Consuming applications are affected when configured to use libvips and accept image uploads from untrusted users. An unauthenticated attacker may exploit this behavior to read arbitrary files accessible to the Rails process, including environment variables and application secrets. Exposure of credentials such as secret_key_base or external-service tokens may enable remote code exec

    • Update to 7.2.3.2
    • Update to 8.0.5.1
    • Update to 8.1.3.1
    Published Updated
  9. CVE-2026-33658

    Low · CVSS 2.3EPSS 0.49%Fix available

    Rails Active Storage has a possible DoS vulnerability in proxy mode via multi-range requests

    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 proxy controller does not limit the number of byte ranges in an HTTP Range header. A request with thousands of small ranges causes disproportionate CPU usage compared to a normal request for the same file, possibly resulting in a DoS vulnerability. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch.

    • Update to 7.2.3.1
    • Update to 8.0.4.1
    • Update to 8.1.2.1
    Published Updated
  10. CVE-2026-33202

    Medium · CVSS 6.6EPSS 0.73%Fix available

    Rails Active Storage has possible glob injection in its 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#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.

    • Update to 7.2.3.1
    • Update to 8.0.4.1
    • Update to 8.1.2.1
    Published Updated
  11. CVE-2026-33195

    High · CVSS 8EPSS 0.64%Fix available

    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.

    • Update to 7.2.3.1
    • Update to 8.0.4.1
    • Update to 8.1.2.1
    Published Updated
  12. CVE-2026-33174

    Medium · CVSS 6.6EPSS 0.68%Fix available

    Rails Active Storage has a possible DoS vulnerability when in proxy mode via Range requests

    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, when serving files through Active Storage's proxy delivery mode, the proxy controller loads the entire requested byte range into memory before sending it. A request with a large or unbounded Range header (e.g. `bytes=0-`) could cause the server to allocate memory proportional to the file size, possibly resulting in a DoS vulnerability through memory exhaustion. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch.

    • Update to 7.2.3.1
    • Update to 8.0.4.1
    • Update to 8.1.2.1
    Published Updated
  13. CVE-2026-33173

    Medium · CVSS 5.3EPSS 0.43%Fix available

    Rails Active Storage has possible content type bypass via metadata in direct uploads

    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.

    • Update to 7.2.3.1
    • Update to 8.0.4.1
    • Update to 8.1.2.1
    Published Updated
  14. CVE-2025-24293

    Critical · CVSS 9.2EPSS 5.58%Public exploitFix available

    CVE-2025-24293

    # Active Storage allowed transformation methods potentially unsafe Active Storage attempts to prevent the use of potentially unsafe image transformation methods and parameters by default. The default allowed list contains three methods allow for the circumvention of the safe defaults which enables potential command injection vulnerabilities in cases where arbitrary user supplied input is accepted as valid transformation methods or parameters. Impact ------ This vulnerability impacts applications that use Active Storage with the image_processing processing gem in addition to mini_magick as the image processor. Vulnerable co

    • Update to 7.1.5.2
    • Update to 7.2.2.2
    • Update to 8.0.2.1
    Published Updated
  15. CVE-2024-26144

    Medium · CVSS 5.3EPSS 1.25%Fix available

    Possible Sensitive Session Information Leak in Active Storage

    Rails is a web-application framework. Starting with version 5.2.0, there is a possible sensitive session information leak in Active Storage. By default, Active Storage sends a Set-Cookie header along with the user's session cookie when serving blobs. It also sets Cache-Control to public. Certain proxies may cache the Set-Cookie, leading to an information leak. The vulnerability is fixed in 7.0.8.1 and 6.1.7.7.

    • Update to 6.1.7.7
    • Update to 7.0.8.1
    Published Updated
  16. CVE-2018-16477

    Medium · CVSS 6.5EPSS 1.31%Fix available

    CVE-2018-16477

    A bypass vulnerability in Active Storage >= 5.2.0 for Google Cloud Storage and Disk services allow an attacker to modify the `content-disposition` and `content-type` parameters which can be used in with HTML files and have them executed inline. Additionally, if combined with other techniques such as cookie bombing and specially crafted AppCache manifests, an attacker can gain access to private signed URLs within a specific storage path. This vulnerability has been fixed in version 5.2.1.1.

    • Update to 5.2.1.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →