Is activeresource 5.1 vulnerable?

RubyGems · 2 releases from 5.1.0 to 5.1.1 · latest activeresource is 6.2.0 · checked 18 Nov 2026

No known advisories in the last release

activeresource 5.1.1, the last 5.1 release, has no known advisories. 1 advisory affects earlier 5.1.x releases, so update to 5.1.1.

Update within 5.1:bundle update --conservative activeresource # Gemfile: '>= 5.1.1'

Is your project on an affected activeresource?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 5.1.x, affecting earlier releases

  • HighCVE-2020-8151GHSA-46j2-xjgp-jrfm21 May 2020

    Information disclosure issue in Active Resource

    Affected
    >=3.0.0.rc <5.1.1
    Fixed in
    5.1.1

Every activeresource 5.1.x release

Affected: 5.1.0. 5.1.1 is not affected. Latest activeresource: 6.2.0.

VersionKnown advisories
activeresource 5.1.1None
activeresource 5.1.0CVE-2020-8151

Which of your client projects are still on activeresource 5.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact activeresource version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other activeresource versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.