VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

actionpack: vulnerability history, versions and safety

actionpack is a package in the RubyGems ecosystem. Vulert records 70 vulnerabilities for it across 120 releases, from Oct 2017 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
70 vulnerabilities recorded H11 M49 L10
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 23 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all actionpack vulnerabilities

Vulert verdict on actionpack 8.1.4 i

Updated on 23 Oct 2026

Careful: 8.1.4 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 8.1.4 — affected i
  • Vulnerabilities on record 70 over 8 years · 1 in the last year i
  • Latest disclosure 23 Mar 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 1 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 actionpack, 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 L1 MIT No Details →
8.1.4 24 Sep 2026 L1 MIT No Details →
8.0.5.1 29 Jul 2026 L1 MIT No Details →
7.2.3.2 29 Jul 2026 L1 MIT No Details →
8.1.3.1 29 Jul 2026 L1 MIT No Details →
8.1.3 24 Mar 2026 L1 MIT No Details →
8.0.5 24 Mar 2026 L1 MIT No Details →
8.1.2.1 23 Mar 2026 L1 MIT No Details →
8.0.4.1 23 Mar 2026 L1 MIT No Details →
7.2.3.1 23 Mar 2026 L1 MIT No Details →
8.1.2 08 Jan 2026 L1 MIT Yes Details →
8.1.1 28 Oct 2025 L1 MIT Yes Details →
8.0.4 28 Oct 2025 L1 MIT No Details →
7.2.3 28 Oct 2025 L1 MIT No Details →
7.1.6 28 Oct 2025 L1 MIT No Details →
7.0.10 28 Oct 2025 L1 MIT No Details →
8.1.0 22 Oct 2025 L1 MIT Yes Details →
8.1.0.rc1 15 Oct 2025 L1 MIT No Details →
8.0.3 22 Sep 2025 L1 MIT No Details →
8.1.0.beta1 04 Sep 2025 L1 MIT No Details →
8.0.2.1 13 Aug 2025 L1 MIT No Details →
7.2.2.2 13 Aug 2025 L1 MIT No Details →
7.1.5.2 13 Aug 2025 L1 MIT No Details →
8.0.2 12 Mar 2025 L1 MIT No Details →
8.0.1 13 Dec 2024 L1 MIT No Details →
8.0.0.1 10 Dec 2024 L1 MIT No Details →
7.2.2.1 10 Dec 2024 L1 MIT No Details →
7.1.5.1 10 Dec 2024 L1 MIT No Details →
7.0.8.7 10 Dec 2024 L1 MIT No Details →
8.0.0 07 Nov 2024 L1 MIT No Details →
7.2.2 31 Oct 2024 L1 MIT No Details →
7.1.5 31 Oct 2024 L1 MIT No Details →
8.0.0.rc2 30 Oct 2024 L1 MIT No Details →
7.2.1.2 23 Oct 2024 L1 MIT No Details →
7.1.4.2 23 Oct 2024 L1 MIT No Details →
7.0.8.6 23 Oct 2024 L2 MIT Yes Details →
6.1.7.10 23 Oct 2024 L2 MIT Yes Details →
8.0.0.rc1 19 Oct 2024 L1 MIT No Details →
6.1.7.9 15 Oct 2024 L2 MIT Yes Details →
7.2.1.1 15 Oct 2024 L1 MIT No Details →
7.1.4.1 15 Oct 2024 L1 MIT No Details →
7.0.8.5 15 Oct 2024 L2 MIT Yes Details →
8.0.0.beta1 26 Sep 2024 L1 MIT No Details →
7.1.4 22 Aug 2024 L1 MIT No Details →
7.2.1 22 Aug 2024 L1 MIT No Details →
7.2.0 09 Aug 2024 L1 MIT No Details →
7.2.0.rc1 06 Aug 2024 L1 MIT No Details →
7.2.0.beta3 11 Jul 2024 L1 MIT No Details →
7.2.0.beta2 04 Jun 2024 L1 MIT No Details →
7.1.3.4 04 Jun 2024 L1 MIT No Details →
7.0.8.4 04 Jun 2024 L2 MIT Yes Details →
6.1.7.8 04 Jun 2024 M2 L4 MIT Yes Details →
7.2.0.beta1 29 May 2024 L1 MIT No Details →
7.0.8.3 17 May 2024 L2 MIT Yes Details →
7.1.3.3 16 May 2024 L1 MIT No Details →
7.0.8.2 16 May 2024 L2 MIT Yes Details →
7.1.3.2 21 Feb 2024 L1 MIT No Details →
7.1.3.1 21 Feb 2024 L1 MIT No Details →
7.0.8.1 21 Feb 2024 L2 MIT Yes Details →
6.1.7.7 21 Feb 2024 M3 L5 MIT No Details →
7.1.3 16 Jan 2024 L1 MIT Yes Details →
7.1.2 10 Nov 2023 L1 MIT Yes Details →
7.1.1 11 Oct 2023 L1 MIT Yes Details →
7.1.0 05 Oct 2023 L1 MIT Yes Details →
7.1.0.rc2 01 Oct 2023 L1 MIT No Details →
7.1.0.rc1 27 Sep 2023 L1 MIT No Details →
7.1.0.beta1 13 Sep 2023 L1 MIT No Details →
7.0.8 09 Sep 2023 M1 L2 MIT Yes Details →
7.0.7.2 22 Aug 2023 M1 L2 MIT Yes Details →
6.1.7.6 22 Aug 2023 M3 L5 MIT No Details →
7.0.7.1 22 Aug 2023 M1 L2 MIT Yes Details →
6.1.7.5 22 Aug 2023 M3 L5 MIT No Details →
7.0.7 09 Aug 2023 M1 L2 MIT Yes Details →
7.0.6 29 Jun 2023 M1 L2 MIT Yes Details →
7.0.5.1 26 Jun 2023 M1 L2 MIT Yes Details →
6.1.7.4 26 Jun 2023 M3 L5 MIT No Details →
7.0.5 24 May 2023 M1 L2 MIT Yes Details →
7.0.4.3 13 Mar 2023 M1 L2 MIT Yes Details →
6.1.7.3 13 Mar 2023 M4 L5 MIT No Details →
6.1.7.2 25 Jan 2023 M4 L5 MIT No Details →
7.0.4.2 25 Jan 2023 M1 L2 MIT Yes Details →
7.0.4.1 17 Jan 2023 M1 L2 MIT Yes Details →
6.1.7.1 17 Jan 2023 M4 L5 MIT No Details →
6.0.6.1 17 Jan 2023 M3 L6 MIT No Details →
7.0.4 09 Sep 2022 M2 L3 MIT No Details →
6.1.7 09 Sep 2022 M4 L6 MIT No Details →
6.0.6 09 Sep 2022 M3 L6 MIT No Details →
7.0.3.1 12 Jul 2022 M2 L3 MIT No Details →
6.1.6.1 12 Jul 2022 M4 L6 MIT No Details →
6.0.5.1 12 Jul 2022 M3 L6 MIT No Details →
5.2.8.1 12 Jul 2022 M3 L7 MIT No Details →
5.2.8 09 May 2022 M3 L7 MIT No Details →
6.0.5 09 May 2022 M3 L6 MIT No Details →
6.1.6 09 May 2022 M4 L6 MIT No Details →
7.0.3 09 May 2022 M2 L3 MIT No Details →
7.0.2.4 26 Apr 2022 M2 L3 MIT No Details →
6.1.5.1 26 Apr 2022 M4 L6 MIT No Details →
6.0.4.8 26 Apr 2022 M3 L6 MIT No Details →
5.2.7.1 26 Apr 2022 M3 L7 MIT No Details →
5.2.7 11 Mar 2022 M4 L7 MIT No Details →
6.1.5 10 Mar 2022 M4 L6 — No Details →
7.0.2.3 08 Mar 2022 M2 L3 — No Details →
6.1.4.7 08 Mar 2022 M4 L6 — No Details →
6.0.4.7 08 Mar 2022 M3 L6 — No Details →
5.2.6.3 08 Mar 2022 M4 L7 — No Details →
7.0.2.2 11 Feb 2022 M2 L3 — No Details →
6.1.4.6 11 Feb 2022 M4 L6 — No Details →
6.0.4.6 11 Feb 2022 M3 L6 — No Details →
5.2.6.2 11 Feb 2022 M4 L7 — No Details →
5.2.6.1 11 Feb 2022 H1 M4 L7 — No Details →
6.0.4.5 11 Feb 2022 M3 L6 — No Details →
6.1.4.5 11 Feb 2022 M4 L6 — No Details →
7.0.2.1 11 Feb 2022 M2 L3 — No Details →
7.0.2 08 Feb 2022 M2 L3 — No Details →
7.0.1 06 Jan 2022 M2 L3 — No Details →
7.0.0 15 Dec 2021 M2 L3 — No Details →
6.1.4.4 15 Dec 2021 M4 L6 — No Details →
6.0.4.4 15 Dec 2021 M3 L6 — No Details →
7.0.0.rc3 14 Dec 2021 L3 — No Details →
6.1.4.3 14 Dec 2021 M4 L6 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 34
  • 2018 7
  • 2020 3
  • 2021 8
  • 2022 4
  • 2023 4
  • 2024 9
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for actionpack

The 5 most severe of 70 vulnerabilities recorded for this package

Search all 70 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-8164: Possible Strong Parameters Bypass in ActionPack 7.5 high 5.2.4.3 26 May 2020
CVE-2021-22904: Possible DoS Vulnerability in Action Controller Token Authentication 7.5 high 6.0.3.7 05 May 2021
CVE-2021-22885: Action Pack Information Disclosure / Unintended Method Execution 7.5 high 6.0.3.7 05 May 2021
CVE-2021-22902: Denial of Service in Action Dispatch 7.5 high 6.0.3.7 05 May 2021
CVE-2015-7581: actionpack - Denial of Service Vulnerability 7.5 high 4.2.5.1 24 Oct 2017

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 actionpack

Is actionpack safe to use?

Vulert records 70 vulnerabilities for actionpack in RubyGems: 0 critical, 11 high, 49 medium and 10 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is actionpack's Vulert package health score?

Vulert scores actionpack 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of actionpack affected?

Yes. 8.1.4, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of actionpack 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 actionpack have?

70 vulnerabilities are recorded for actionpack in the RubyGems ecosystem: 0 critical, 11 high, 49 medium and 10 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new actionpack vulnerabilities disclosed?

1 vulnerability was recorded for actionpack in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 actionpack 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 actionpack for upcoming vulnerabilities?

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