VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

activestorage: vulnerability history, versions and safety

activestorage is a package in the RubyGems ecosystem. Vulert records 11 vulnerabilities for it across 108 releases, from Dec 2018 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded C3 H2 M5 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 30 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all activestorage vulnerabilities

Vulert verdict on activestorage 8.1.4 i

Updated on 23 Oct 2026

Good news: 8.1.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 11.

Package health score 74/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 8.1.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 8.1.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 8.1.4 — unaffected i
  • Vulnerabilities on record 11 over 7 years · 6 in the last year i
  • Latest disclosure 30 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 58,837 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 22 Oct 2026. Licence information is not legal advice.

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.

01 Versions

Which versions are affected

Every version Vulert tracks for activestorage, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.2.4 24 Sep 2026 none MIT — Details →
8.1.4 24 Sep 2026 none MIT — Details →
8.0.5.1 29 Jul 2026 none MIT — Details →
7.2.3.2 29 Jul 2026 none MIT — Details →
8.1.3.1 29 Jul 2026 none MIT — Details →
8.1.3 24 Mar 2026 none MIT — Details →
8.0.5 24 Mar 2026 none MIT — Details →
8.1.2.1 23 Mar 2026 none MIT — Details →
8.0.4.1 23 Mar 2026 none MIT — Details →
7.2.3.1 23 Mar 2026 C1 MIT Yes Details →
8.1.2 08 Jan 2026 H1 M3 L1 MIT Yes Details →
8.1.1 28 Oct 2025 H1 M3 L1 MIT Yes Details →
8.0.4 28 Oct 2025 none MIT — Details →
7.2.3 28 Oct 2025 C1 MIT Yes Details →
7.1.6 28 Oct 2025 C1 MIT Yes Details →
7.0.10 28 Oct 2025 C1 MIT Yes Details →
8.1.0 22 Oct 2025 H1 M3 L1 MIT Yes Details →
8.1.0.rc1 15 Oct 2025 H1 M3 MIT Yes Details →
8.0.3 22 Sep 2025 none MIT — Details →
8.1.0.beta1 04 Sep 2025 H1 M3 MIT Yes Details →
8.0.2.1 13 Aug 2025 none MIT — Details →
7.2.2.2 13 Aug 2025 C1 MIT Yes Details →
7.1.5.2 13 Aug 2025 C1 MIT Yes Details →
8.0.2 12 Mar 2025 C1 MIT Yes Details →
8.0.1 13 Dec 2024 C1 MIT Yes Details →
8.0.0.1 10 Dec 2024 C1 MIT Yes Details →
7.2.2.1 10 Dec 2024 C1 MIT Yes Details →
7.1.5.1 10 Dec 2024 C1 MIT Yes Details →
7.0.8.7 10 Dec 2024 C1 MIT Yes Details →
8.0.0 07 Nov 2024 C1 MIT Yes Details →
7.2.2 31 Oct 2024 C1 MIT Yes Details →
7.1.5 31 Oct 2024 C1 MIT Yes Details →
8.0.0.rc2 30 Oct 2024 C1 MIT Yes Details →
7.2.1.2 23 Oct 2024 C1 MIT Yes Details →
7.1.4.2 23 Oct 2024 C1 MIT Yes Details →
7.0.8.6 23 Oct 2024 C1 MIT Yes Details →
6.1.7.10 23 Oct 2024 C1 MIT Yes Details →
8.0.0.rc1 19 Oct 2024 C1 MIT Yes Details →
6.1.7.9 15 Oct 2024 C1 MIT Yes Details →
7.2.1.1 15 Oct 2024 C1 MIT Yes Details →
7.1.4.1 15 Oct 2024 C1 MIT Yes Details →
7.0.8.5 15 Oct 2024 C1 MIT Yes Details →
8.0.0.beta1 26 Sep 2024 C1 MIT Yes Details →
7.1.4 22 Aug 2024 C1 MIT Yes Details →
7.2.1 22 Aug 2024 C1 MIT Yes Details →
7.2.0 09 Aug 2024 C1 MIT Yes Details →
7.2.0.rc1 06 Aug 2024 C1 MIT Yes Details →
7.2.0.beta3 11 Jul 2024 C1 MIT Yes Details →
7.2.0.beta2 04 Jun 2024 C1 MIT Yes Details →
7.1.3.4 04 Jun 2024 C1 MIT Yes Details →
7.0.8.4 04 Jun 2024 C1 MIT Yes Details →
6.1.7.8 04 Jun 2024 C1 MIT Yes Details →
7.2.0.beta1 29 May 2024 C1 MIT Yes Details →
7.0.8.3 17 May 2024 C1 MIT Yes Details →
7.1.3.3 16 May 2024 C1 MIT Yes Details →
7.0.8.2 16 May 2024 C1 MIT Yes Details →
7.1.3.2 21 Feb 2024 C1 MIT Yes Details →
7.1.3.1 21 Feb 2024 C1 MIT Yes Details →
7.0.8.1 21 Feb 2024 C1 MIT Yes Details →
6.1.7.7 21 Feb 2024 C1 MIT Yes Details →
7.1.3 16 Jan 2024 C1 MIT Yes Details →
7.1.2 10 Nov 2023 C1 MIT Yes Details →
7.1.1 11 Oct 2023 C1 MIT Yes Details →
7.1.0 05 Oct 2023 C1 MIT Yes Details →
7.1.0.rc2 01 Oct 2023 C1 MIT Yes Details →
7.1.0.rc1 27 Sep 2023 C1 MIT Yes Details →
7.1.0.beta1 13 Sep 2023 C1 MIT Yes Details →
7.0.8 09 Sep 2023 C1 MIT Yes Details →
7.0.7.2 22 Aug 2023 C1 MIT Yes Details →
6.1.7.6 22 Aug 2023 C1 M1 MIT Yes Details →
7.0.7.1 22 Aug 2023 C1 MIT Yes Details →
6.1.7.5 22 Aug 2023 C1 M1 MIT Yes Details →
7.0.7 09 Aug 2023 C1 MIT Yes Details →
7.0.6 29 Jun 2023 C1 MIT Yes Details →
7.0.5.1 26 Jun 2023 C1 MIT Yes Details →
6.1.7.4 26 Jun 2023 C1 M1 MIT Yes Details →
7.0.5 24 May 2023 C1 MIT Yes Details →
7.0.4.3 13 Mar 2023 C1 MIT Yes Details →
6.1.7.3 13 Mar 2023 C1 M1 MIT Yes Details →
6.1.7.2 25 Jan 2023 C1 M1 MIT Yes Details →
7.0.4.2 25 Jan 2023 C1 MIT Yes Details →
7.0.4.1 17 Jan 2023 C1 MIT Yes Details →
6.1.7.1 17 Jan 2023 C1 M1 MIT Yes Details →
6.0.6.1 17 Jan 2023 C1 M1 MIT Yes Details →
7.0.4 09 Sep 2022 C1 MIT Yes Details →
6.1.7 09 Sep 2022 C1 M1 MIT Yes Details →
6.0.6 09 Sep 2022 C1 M1 MIT Yes Details →
7.0.3.1 12 Jul 2022 C1 MIT Yes Details →
6.1.6.1 12 Jul 2022 C1 M1 MIT Yes Details →
6.0.5.1 12 Jul 2022 C1 M1 MIT Yes Details →
5.2.8.1 12 Jul 2022 C1 M1 MIT Yes Details →
5.2.8 09 May 2022 C1 M1 MIT Yes Details →
6.0.5 09 May 2022 C1 M1 MIT Yes Details →
6.1.6 09 May 2022 C1 M1 MIT Yes Details →
7.0.3 09 May 2022 C1 MIT Yes Details →
7.0.2.4 26 Apr 2022 C1 MIT Yes Details →
6.1.5.1 26 Apr 2022 C1 M1 MIT Yes Details →
6.0.4.8 26 Apr 2022 C1 M1 MIT Yes Details →
5.2.7.1 26 Apr 2022 C1 M1 MIT Yes Details →
5.2.7 11 Mar 2022 C1 M1 MIT Yes Details →
6.1.5 10 Mar 2022 C1 M1 — Yes Details →
7.0.2.3 08 Mar 2022 C1 — Yes Details →
6.1.4.7 08 Mar 2022 C1 M1 — Yes Details →
6.0.4.7 08 Mar 2022 C1 M1 — Yes Details →
5.2.6.3 08 Mar 2022 C1 M1 — Yes Details →
7.0.2.2 11 Feb 2022 C1 — Yes Details →
6.1.4.6 11 Feb 2022 C1 M1 — Yes Details →
6.0.4.6 11 Feb 2022 C1 M1 — Yes Details →
5.2.6.2 11 Feb 2022 C2 M1 — Yes Details →
5.2.6.1 11 Feb 2022 C2 M1 — Yes Details →
6.0.4.5 11 Feb 2022 C1 M1 — Yes Details →
6.1.4.5 11 Feb 2022 C1 M1 — Yes Details →
7.0.2.1 11 Feb 2022 C1 — Yes Details →
7.0.2 08 Feb 2022 C1 — Yes Details →
7.0.1 06 Jan 2022 C1 — Yes Details →
7.0.0 15 Dec 2021 C1 — Yes Details →
6.1.4.4 15 Dec 2021 C1 M1 — Yes Details →
6.0.4.4 15 Dec 2021 C1 M1 — Yes Details →
7.0.0.rc3 14 Dec 2021 C1 — Yes Details →
6.1.4.3 14 Dec 2021 C1 M1 — Yes Details →

The newest 120 of 186 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2020 1
  • 2022 1
  • 2024 1
  • 2025 1
  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 6 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for activestorage

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-21831: Possible code injection vulnerability in Rails / Active Storage 9.8 critical 5.2.6.3 08 Mar 2022
CVE-2026-66066: Active Storage Arbitrary File Read and Remote Code Execution Vulnerability 9.5 critical 7.2.3.2 30 Jul 2026
CVE-2025-24293: Active Storage Command Injection Vulnerability 9.2 critical 8.0.2.1 14 Aug 2025
CVE-2026-33195: Rails Active Storage Path Traversal Vulnerability 8.0 high 8.1.2.1 23 Mar 2026
CVE-2020-8162: Circumvention of file size limits in ActiveStorage 7.5 high 5.2.4.3 26 May 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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

About activestorage

Is activestorage safe to use?

Vulert records 11 vulnerabilities for activestorage in RubyGems: 3 critical, 2 high, 5 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is activestorage's Vulert package health score?

Vulert scores activestorage 74/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of activestorage affected?

No. 8.1.4, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of activestorage should I use?

8.1.4 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does activestorage have?

11 vulnerabilities are recorded for activestorage in the RubyGems ecosystem: 3 critical, 2 high, 5 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new activestorage vulnerabilities disclosed?

6 vulnerabilities were recorded for activestorage in the last 12 months, and the oldest entry in this database dates to 05 Dec 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of activestorage are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor activestorage for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the activestorage version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.