VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

activeadmin: vulnerability history, versions and safety

activeadmin is a package in the RubyGems ecosystem. Vulert records 4 vulnerabilities for it across 69 releases, from Dec 2023 to Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H3 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all activeadmin vulnerabilities

Vulert verdict on activeadmin 3.5.2 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 3.5.2 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 02 Jun 2024 i
  • Highest CVSS 8.4 i
  • With no published fix 0 i
  • Stars 9,714 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 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 activeadmin, 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
4.0.0.beta23 20 Sep 2026 none MIT — Details →
3.5.2 13 Jul 2026 none MIT — Details →
3.5.1 24 Mar 2026 none MIT — Details →
3.5.0 09 Mar 2026 none MIT — Details →
4.0.0.beta22 07 Mar 2026 none MIT — Details →
4.0.0.beta21 05 Feb 2026 none MIT — Details →
4.0.0.beta20 27 Jan 2026 none MIT — Details →
4.0.0.beta19 20 Nov 2025 none MIT — Details →
3.4.0 03 Nov 2025 none MIT — Details →
4.0.0.beta18 01 Nov 2025 none MIT — Details →
4.0.0.beta17 21 Oct 2025 none MIT — Details →
4.0.0.beta16 23 Jul 2025 none MIT — Details →
3.3.0 08 Mar 2025 none MIT — Details →
4.0.0.beta15 07 Dec 2024 none MIT — Details →
4.0.0.beta14 25 Nov 2024 none MIT — Details →
4.0.0.beta13 24 Sep 2024 none MIT — Details →
4.0.0.beta12 15 Sep 2024 none MIT — Details →
3.2.5 05 Sep 2024 none MIT — Details →
4.0.0.beta11 31 Aug 2024 none MIT — Details →
3.2.4 24 Aug 2024 none MIT — Details →
4.0.0.beta10 24 Aug 2024 none MIT — Details →
4.0.0.beta9 04 Aug 2024 none MIT — Details →
3.2.3 02 Aug 2024 none MIT — Details →
4.0.0.beta8 27 Jul 2024 none MIT — Details →
4.0.0.beta7 31 May 2024 none MIT — Details →
3.2.2 31 May 2024 none MIT — Details →
4.0.0.beta6 03 May 2024 none MIT — Details →
3.2.1 02 May 2024 H1 MIT Yes Details →
4.0.0.beta5 14 Feb 2024 none MIT — Details →
4.0.0.beta4 17 Jan 2024 none MIT — Details →
4.0.0.beta3 06 Jan 2024 none MIT — Details →
4.0.0.beta2 06 Jan 2024 none MIT — Details →
4.0.0.beta1 06 Jan 2024 none MIT — Details →
3.2.0 11 Dec 2023 H1 MIT Yes Details →
3.1.0 23 Oct 2023 H2 M1 MIT Yes Details →
3.0.0 15 Jul 2023 H2 M1 MIT Yes Details →
2.14.0 22 Jun 2023 H2 M1 MIT Yes Details →
2.13.1 20 May 2022 H2 M1 MIT Yes Details →
2.13.0 07 May 2022 H2 M1 MIT Yes Details →
2.12.0 22 Apr 2022 H2 M1 MIT Yes Details →
2.11.2 12 Apr 2022 H3 M1 MIT Yes Details →
2.11.1 25 Mar 2022 H3 M1 MIT Yes Details →
2.11.0 11 Mar 2022 H3 M1 MIT Yes Details →
2.10.1 25 Feb 2022 H3 M1 MIT Yes Details →
2.10.0 11 Feb 2022 H3 M1 MIT Yes Details →
2.9.0 14 Dec 2020 H3 M1 MIT Yes Details →
2.8.1 28 Sep 2020 H3 M1 MIT Yes Details →
2.8.0 04 Sep 2020 H3 M1 MIT Yes Details →
2.7.0 31 Mar 2020 H3 M1 MIT Yes Details →
2.6.1 03 Feb 2020 H3 M1 MIT Yes Details →
2.6.0 16 Dec 2019 H3 M1 MIT Yes Details →
2.5.0 26 Nov 2019 H3 M1 MIT Yes Details →
2.4.0 03 Oct 2019 H3 M1 MIT Yes Details →
2.3.1 13 Sep 2019 H3 M1 MIT Yes Details →
2.3.0 12 Sep 2019 H3 M1 MIT Yes Details →
2.2.0 15 Jul 2019 H3 M1 MIT Yes Details →
2.1.0 10 Jun 2019 H3 M1 MIT Yes Details →
2.0.0 25 Apr 2019 H3 M1 MIT Yes Details →
2.0.0.rc2 13 Apr 2019 H3 M1 MIT Yes Details →
2.0.0.rc1 23 Mar 2019 H3 M1 MIT Yes Details →
1.4.3 04 Dec 2018 H3 M1 MIT Yes Details →
1.4.2 26 Nov 2018 H3 M1 MIT Yes Details →
1.4.1 23 Nov 2018 H3 M1 MIT Yes Details →
1.4.0 18 Nov 2018 H3 M1 MIT Yes Details →
1.3.1 11 Aug 2018 H3 M1 MIT Yes Details →
1.3.0 20 Apr 2018 H3 M1 MIT Yes Details →
1.2.1 10 Jan 2018 H3 M1 MIT Yes Details →
1.2.0 19 Dec 2017 H3 M1 MIT Yes Details →
1.1.0 25 Jul 2017 H3 M1 MIT Yes Details →
1.0.0 25 Apr 2017 H3 M1 MIT Yes Details →
1.0.0.pre5 07 Mar 2017 H3 M1 MIT Yes Details →
1.0.0.pre4 01 Jul 2016 H3 M1 MIT Yes Details →
1.0.0.pre3 30 Jun 2016 H3 M1 MIT Yes Details →
1.0.0.pre2 23 Sep 2015 H3 M1 MIT Yes Details →
1.0.0.pre1 12 Mar 2015 H3 M1 MIT Yes Details →
0.6.6 02 Feb 2015 H3 M1 MIT Yes Details →
0.6.5 28 Jan 2015 H3 M1 MIT Yes Details →
0.6.4 15 Jan 2015 H3 M1 MIT Yes Details →
0.6.3 30 Jan 2014 H3 M1 MIT Yes Details →
0.6.2 21 Oct 2013 H3 M1 MIT Yes Details →
0.6.1 24 Sep 2013 H3 M1 MIT Yes Details →
0.6.0 04 Apr 2013 H3 M1 MIT Yes Details →
0.5.1 06 Dec 2012 H3 M1 — Yes Details →
0.5.0 31 Aug 2012 H3 M1 — Yes Details →
0.5.0.pre1 31 Aug 2012 H3 M1 — Yes Details →
0.5.0.pre 31 Aug 2012 H3 M1 — Yes Details →
0.4.4 09 May 2012 H3 M1 — Yes Details →
0.4.3 08 Mar 2012 H3 M1 — Yes Details →
0.4.2 21 Feb 2012 H3 M1 — Yes Details →
0.4.1 16 Feb 2012 H3 M1 — Yes Details →
0.4.0 30 Jan 2012 H3 M1 — Yes Details →
0.3.4 08 Nov 2011 H3 M1 — Yes Details →
0.3.3 29 Oct 2011 H3 M1 — Yes Details →
0.3.2 23 Sep 2011 H3 M1 — Yes Details →
0.3.1 02 Sep 2011 H3 M1 — Yes Details →
0.3.0 25 Aug 2011 H3 M1 — Yes Details →
0.2.2 27 May 2011 H3 M1 — Yes Details →
0.2.1 12 May 2011 H3 M1 — Yes Details →
0.2.0 12 May 2011 H3 M1 — Yes Details →
0.1.1 15 Sep 2010 H3 M1 — Yes Details →
0.1.0 07 Sep 2010 H3 M1 — Yes Details →

All 101 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 3
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for activeadmin

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-50448: Potential CSV export data leak in activeadmin 8.4 high 2.12.0 15 Dec 2023
Duplicate Advisory: ActiveAdmin vulnerable to CSV injection 8.4 high 3.2.0 24 Dec 2023
CVE-2024-37031: Stored Persistent Cross-Site Scripting (XSS) in ActiveAdmin 7.2 high 3.2.2 02 Jun 2024
CVE-2023-51763: ActiveAdmin CSV Injection leading to sensitive information disclosure 5.2 medium 3.2.0 28 Dec 2023

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 activeadmin

Is activeadmin safe to use?

Vulert records 4 vulnerabilities for activeadmin in RubyGems: 0 critical, 3 high, 1 medium and 0 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 activeadmin's Vulert package health score?

Vulert scores activeadmin 81/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 activeadmin affected?

No. 3.5.2, 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 activeadmin should I use?

3.5.2 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 activeadmin have?

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

How often are new activeadmin vulnerabilities disclosed?

0 vulnerabilities were recorded for activeadmin in the last 12 months, and the oldest entry in this database dates to 15 Dec 2023. 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 activeadmin 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 activeadmin for upcoming vulnerabilities?

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