Is activejob 0.0 vulnerable?

RubyGems · 1 release from 0.0.0 to 0.0.0 · latest activejob is 8.1.4.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. activejob 0.0.0, the last 0.0 release, is affected by 1 known security advisory (1 medium). Upgrade to 4.2.0.beta2 or later to fix all of them.

Upgrade with:bundle update --conservative activejob # Gemfile: '>= 4.2.0.beta2'

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

Advisories affecting activejob 0.0.0

  • MediumGHSA-mpwp-4h2m-765c16 Jan 2026

    Active Job - Object injection security vulnerability

    Affected
    <4.2.0.beta2
    Fixed in
    4.2.0.beta2

Which of your client projects are still on activejob 0.0?

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.