Is activejob 5.1 vulnerable?

RubyGems · 10 releases from 5.1.0 to 5.1.7 · latest activejob is 8.1.4.1 · checked 18 Nov 2026

No known advisories in the last release

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

Update within 5.1:bundle update --conservative activejob # Gemfile: '>= 5.1.7'

Is your project on an affected activejob?

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-2018-16476GHSA-q2qw-rmrh-vv425 Dec 2018

    Improper Access Control in activejob

    Affected
    >=4.2.0 <4.2.11 · >=5.0.0 <5.0.7.1 · >=5.1.0 <5.1.6.1 · >=5.2.0 <5.2.1.1
    Fixed in
    4.2.11, 5.0.7.1, 5.1.6.1, 5.2.1.1

Every activejob 5.1.x release

Affected: 5.1.0 to 5.1.6. 5.1.6.1 and later are not affected. Latest activejob: 8.1.4.1.

VersionKnown advisories
activejob 5.1.7None
activejob 5.1.6.2None
activejob 5.1.6.1None
activejob 5.1.6CVE-2018-16476
activejob 5.1.5CVE-2018-16476
activejob 5.1.4CVE-2018-16476
activejob 5.1.3CVE-2018-16476
activejob 5.1.2CVE-2018-16476
activejob 5.1.1CVE-2018-16476
activejob 5.1.0CVE-2018-16476

Which of your client projects are still on activejob 5.1?

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

Other activejob 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.