activestorage vulnerabilities — 11 matching vulnerabilities

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed — no installation and no source-code access required.

Scan your app free →
Severity Vulnerability Package Ecosystem Disclosed Fixed version
9.5 critical CVE-2026-66066: Active Storage Arbitrary File Read and Remote Code Execution Vulnerability activestorage RubyGems 30 Jul 2026 7.2.3.2
2.3 low CVE-2026-33658: Rails Active Storage DoS Vulnerability via Multi-Range Requests activestorage RubyGems 25 Mar 2026 8.1.2.1
6.6 medium CVE-2026-33202: Rails Active Storage DiskService Glob Injection Vulnerability activestorage RubyGems 23 Mar 2026 8.1.2.1
8.0 high CVE-2026-33195: Rails Active Storage Path Traversal Vulnerability activestorage RubyGems 23 Mar 2026 8.1.2.1
6.6 medium CVE-2026-33174: Rails Active Storage DoS Vulnerability via Range Requests activestorage RubyGems 23 Mar 2026 8.1.2.1
5.3 medium CVE-2026-33173: Rails Active Storage Content Type Bypass via Metadata in Direct Uploads activestorage RubyGems 23 Mar 2026 8.1.2.1
9.2 critical CVE-2025-24293: Active Storage Command Injection Vulnerability activestorage RubyGems 14 Aug 2025 8.0.2.1
5.3 medium CVE-2024-26144: Rails Active Storage Sensitive Session Information Leak activestorage RubyGems 27 Feb 2024 6.1.7.7
9.8 critical CVE-2022-21831: Possible code injection vulnerability in Rails / Active Storage activestorage RubyGems 08 Mar 2022 5.2.6.3
7.5 high CVE-2020-8162: Circumvention of file size limits in ActiveStorage activestorage RubyGems 26 May 2020 5.2.4.3
6.5 medium CVE-2018-16477: activestorage - Exposure of Sensitive Information to an Unauthorized Actor activestorage RubyGems 05 Dec 2018 5.2.1.1
Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

Searching the database

How do I search for a CVE or a package?

Type a CVE id, package name, ecosystem or keyword into the search field. Results include the severity, the affected package, the ecosystem, the disclosure date and the fixed version.

Can I filter by severity or by whether a fix exists?

Yes. The filters on the left narrow the list to critical, high, medium or low vulnerabilities, to a single ecosystem, and to vulnerabilities that have a fix available or none yet.

What does "No fix published" mean?

No patched version has been released for that vulnerability yet. The vulnerability page still shows the affected range and any workaround that can reduce exposure in the meantime.