VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

activeresource: vulnerability history, versions and safety

activeresource is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 106 releases, first recorded in May 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 activeresource vulnerabilities

Vulert verdict on activeresource 6.2.0 i

Updated on 23 Oct 2026

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

Package health score 72/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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

  • Current release 6.2.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 21 May 2020 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 1,410 i
  • OpenSSF scorecard 3/10 i
  • Last release 13 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 activeresource, 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
6.2.0 11 Sep 2025 none MIT — Details →
6.1.4 31 Oct 2024 none MIT — Details →
6.1.3 06 Oct 2024 none MIT — Details →
6.1.2 03 Oct 2024 none MIT — Details →
6.1.1 09 Sep 2024 none MIT — Details →
6.1.0 24 Jan 2024 none MIT — Details →
6.0.0 10 Jan 2022 none MIT — Details →
5.1.1 05 May 2020 none MIT — Details →
5.1.0 02 Nov 2018 H1 MIT Yes Details →
5.0.0 05 May 2017 H1 MIT Yes Details →
3.2.22.5 14 Sep 2016 H1 MIT Yes Details →
3.2.22.4 11 Aug 2016 H1 MIT Yes Details →
3.2.22.3 11 Aug 2016 H1 MIT Yes Details →
4.1.0 10 Jun 2016 H1 MIT Yes Details →
3.2.22.2 29 Feb 2016 H1 MIT Yes Details →
3.2.22.1 25 Jan 2016 H1 MIT Yes Details →
3.2.22 16 Jun 2015 H1 MIT Yes Details →
3.2.21 17 Nov 2014 H1 MIT Yes Details →
3.2.20 30 Oct 2014 H1 MIT Yes Details →
3.2.19 02 Jul 2014 H1 MIT Yes Details →
3.2.18 06 May 2014 H1 MIT Yes Details →
3.2.17 18 Feb 2014 H1 MIT Yes Details →
3.2.16 03 Dec 2013 H1 MIT Yes Details →
3.2.15 16 Oct 2013 H1 MIT Yes Details →
3.2.15.rc3 11 Oct 2013 H1 MIT Yes Details →
3.2.15.rc2 04 Oct 2013 H1 MIT Yes Details →
3.2.15.rc1 03 Oct 2013 H1 MIT Yes Details →
3.2.14 22 Jul 2013 H1 MIT Yes Details →
3.2.14.rc2 16 Jul 2013 H1 MIT Yes Details →
3.2.14.rc1 13 Jul 2013 H1 MIT Yes Details →
4.0.0 26 Jun 2013 H1 MIT Yes Details →
3.2.13 18 Mar 2013 H1 — Yes Details →
3.1.12 18 Mar 2013 H1 — Yes Details →
2.3.18 18 Mar 2013 none — — Details →
3.2.13.rc2 06 Mar 2013 H1 — Yes Details →
4.0.0.beta1 03 Mar 2013 H1 MIT Yes Details →
3.2.13.rc1 27 Feb 2013 H1 — Yes Details →
3.2.12 11 Feb 2013 H1 — Yes Details →
3.1.11 11 Feb 2013 H1 — Yes Details →
2.3.17 11 Feb 2013 none — — Details →
3.0.20 28 Jan 2013 H1 — Yes Details →
2.3.16 28 Jan 2013 none — — Details →
3.2.11 08 Jan 2013 H1 — Yes Details →
3.1.10 08 Jan 2013 H1 — Yes Details →
3.0.19 08 Jan 2013 H1 — Yes Details →
2.3.15 08 Jan 2013 none — — Details →
3.2.10 02 Jan 2013 H1 — Yes Details →
3.1.9 02 Jan 2013 H1 — Yes Details →
3.0.18 02 Jan 2013 H1 — Yes Details →
3.2.9 12 Nov 2012 H1 — Yes Details →
3.2.9.rc3 09 Nov 2012 H1 — Yes Details →
3.2.9.rc2 01 Nov 2012 H1 — Yes Details →
3.2.9.rc1 29 Oct 2012 H1 — Yes Details →
3.2.8 09 Aug 2012 H1 — Yes Details →
3.1.8 09 Aug 2012 H1 — Yes Details →
3.0.17 09 Aug 2012 H1 — Yes Details →
3.2.8.rc2 03 Aug 2012 H1 — Yes Details →
3.2.8.rc1 01 Aug 2012 H1 — Yes Details →
3.2.7 26 Jul 2012 H1 — Yes Details →
3.1.7 26 Jul 2012 H1 — Yes Details →
3.0.16 26 Jul 2012 H1 — Yes Details →
3.2.7.rc1 23 Jul 2012 H1 — Yes Details →
3.0.15 13 Jun 2012 H1 — Yes Details →
3.2.6 12 Jun 2012 H1 — Yes Details →
3.1.6 12 Jun 2012 H1 — Yes Details →
3.0.14 12 Jun 2012 H1 — Yes Details →
3.2.5 01 Jun 2012 H1 — Yes Details →
3.2.4 31 May 2012 H1 — Yes Details →
3.1.5 31 May 2012 H1 — Yes Details →
3.0.13 31 May 2012 H1 — Yes Details →
3.2.4.rc1 28 May 2012 H1 — Yes Details →
3.1.5.rc1 28 May 2012 H1 — Yes Details →
3.0.13.rc1 28 May 2012 H1 — Yes Details →
3.2.3 30 Mar 2012 H1 — Yes Details →
3.2.3.rc2 29 Mar 2012 H1 — Yes Details →
3.2.3.rc1 27 Mar 2012 H1 — Yes Details →
3.2.2 01 Mar 2012 H1 — Yes Details →
3.1.4 01 Mar 2012 H1 — Yes Details →
3.0.12 01 Mar 2012 H1 — Yes Details →
3.2.2.rc1 22 Feb 2012 H1 — Yes Details →
3.1.4.rc1 22 Feb 2012 H1 — Yes Details →
3.0.12.rc1 22 Feb 2012 H1 — Yes Details →
3.2.1 26 Jan 2012 H1 — Yes Details →
3.2.0 20 Jan 2012 H1 — Yes Details →
3.2.0.rc2 04 Jan 2012 H1 — Yes Details →
3.2.0.rc1 20 Dec 2011 H1 — Yes Details →
3.1.3 20 Nov 2011 H1 — Yes Details →
3.1.2 18 Nov 2011 H1 — Yes Details →
3.0.11 18 Nov 2011 H1 — Yes Details →
3.1.2.rc2 14 Nov 2011 H1 — Yes Details →
3.1.2.rc1 14 Nov 2011 H1 — Yes Details →
3.1.1 07 Oct 2011 H1 — Yes Details →
3.1.1.rc3 06 Oct 2011 H1 — Yes Details →
3.1.1.rc2 29 Sep 2011 H1 — Yes Details →
3.1.1.rc1 15 Sep 2011 H1 — Yes Details →
3.1.0 31 Aug 2011 H1 — Yes Details →
3.1.0.rc8 29 Aug 2011 H1 — Yes Details →
3.1.0.rc6 16 Aug 2011 H1 — Yes Details →
3.0.10 16 Aug 2011 H1 — Yes Details →
2.3.14 16 Aug 2011 none — — Details →
3.0.10.rc1 05 Aug 2011 H1 — Yes Details →
3.1.0.rc5 25 Jul 2011 H1 — Yes Details →
3.0.9 16 Jun 2011 H1 — Yes Details →
3.0.9.rc5 12 Jun 2011 H1 — Yes Details →
3.0.9.rc4 12 Jun 2011 H1 — Yes Details →
3.1.0.rc4 09 Jun 2011 H1 — Yes Details →
3.0.9.rc3 09 Jun 2011 H1 — Yes Details →
3.1.0.rc3 08 Jun 2011 H1 — Yes Details →
3.0.9.rc1 08 Jun 2011 H1 — Yes Details →
2.3.12 08 Jun 2011 none — — Details →
3.1.0.rc2 08 Jun 2011 H1 — Yes Details →
3.0.8 08 Jun 2011 H1 — Yes Details →
3.0.8.rc4 31 May 2011 H1 — Yes Details →
3.0.8.rc2 27 May 2011 H1 — Yes Details →
3.0.8.rc1 26 May 2011 H1 — Yes Details →
3.1.0.rc1 22 May 2011 H1 — Yes Details →
3.1.0.beta1 05 May 2011 H1 — Yes Details →
3.0.7 18 Apr 2011 H1 — Yes Details →
3.0.7.rc2 15 Apr 2011 H1 — Yes Details →
3.0.7.rc1 14 Apr 2011 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for activeresource

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-8151: Information disclosure issue in Active Resource 7.5 high 5.1.1 21 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 activeresource

Is activeresource safe to use?

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

Vulert scores activeresource 72/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 activeresource affected?

No. 6.2.0, 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 activeresource should I use?

6.2.0 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 activeresource have?

1 vulnerability is recorded for activeresource in the RubyGems ecosystem: 0 critical, 1 high, 0 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 activeresource vulnerabilities disclosed?

0 vulnerabilities were recorded for activeresource in the last 12 months, and the oldest entry in this database dates to 21 May 2020. 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 activeresource 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 activeresource for upcoming vulnerabilities?

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