Is activerecord 4.2 vulnerable?

RubyGems · 18 releases from 4.2.0 to 4.2.11.3 · latest activerecord is 8.1.4.1 · checked 18 Nov 2026

Yes: 3 known advisories

Yes. activerecord 4.2.11.3, the last 4.2 release, is affected by 3 known security advisories (1 critical, 1 high, 1 medium), including CVE-2022-32224, CVE-2022-44566, CVE-2025-55193. 2 more affect earlier 4.2.x releases. Upgrade to 7.1.5.2 or later to fix all of them.

Upgrade with:bundle update --conservative activerecord # Gemfile: '>= 7.1.5.2'

Is your project on an affected activerecord?

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 activerecord 4.2.11.3

  • MediumCVE-2025-55193GHSA-76r7-hhxj-r77613 Aug 2025

    Active Record logging vulnerable to ANSI escape injection

    Affected
    >=8.0 <8.0.2.1 · >=7.2 <7.2.2.2 · <7.1.5.2
    Fixed in
    7.1.5.2, 7.2.2.2, 8.0.2.1
  • HighCVE-2022-44566GHSA-579w-22j4-474918 Jan 2023

    Denial of Service Vulnerability in ActiveRecord's PostgreSQL adapter

    Affected
    <6.1.7.1 · >=7.0.0 <7.0.4.1
    Fixed in
    6.1.7.1, 7.0.4.1
  • CriticalCVE-2022-32224GHSA-3hhc-qp5v-9p2j12 Jul 2022

    Active Record RCE bug with Serialized Columns

    Affected
    >=7.0.0 <7.0.3.1 · >=6.1.0 <6.1.6.1 · >=6.0.0 <6.0.5.1 · <5.2.8.1
    Fixed in
    5.2.8.1, 6.0.5.1, 6.1.6.1, 7.0.3.1

Fixed within 4.2.x, affecting earlier releases

  • MediumCVE-2015-7577GHSA-xrr6-3pc4-m44724 Oct 2017

    Active Record Improper Access Control

    Affected
    >=3.1.0 <3.2.22.1 · >=4.0.0 <4.1.14.1 · >=4.2.0 <4.2.5.1 · >=5.0.0.beta1 <5.0.0.beta1.1
    Fixed in
    3.2.22.1, 4.1.14.1, 4.2.5.1, 5.0.0.beta1.1
  • HighCVE-2016-6317GHSA-pr3r-4wrp-r2pv24 Oct 2017

    ActiveRecord in Ruby on Rails allows database-query bypass

    Affected
    >=4.2.0 <4.2.7.1
    Fixed in
    4.2.7.1

Every activerecord 4.2.x release

Affected: 4.2.0 to 4.2.11.3. Latest activerecord: 8.1.4.1.

VersionKnown advisories
activerecord 4.2.11.3CVE-2025-55193, CVE-2022-44566, CVE-2022-32224
activerecord 4.2.11.2CVE-2025-55193, CVE-2022-44566, CVE-2022-32224
activerecord 4.2.11.1CVE-2025-55193, CVE-2022-44566, CVE-2022-32224
activerecord 4.2.11CVE-2025-55193, CVE-2022-44566, CVE-2022-32224
activerecord 4.2.10CVE-2025-55193, CVE-2022-44566, CVE-2022-32224
activerecord 4.2.9CVE-2025-55193, CVE-2022-44566, CVE-2022-32224
activerecord 4.2.8CVE-2025-55193, CVE-2022-44566, CVE-2022-32224
activerecord 4.2.7.1CVE-2025-55193, CVE-2022-44566, CVE-2022-32224
activerecord 4.2.7CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2016-6317
activerecord 4.2.6CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2016-6317
activerecord 4.2.5.2CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2016-6317
activerecord 4.2.5.1CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2016-6317
activerecord 4.2.5CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2015-7577, CVE-2016-6317
activerecord 4.2.4CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2015-7577, CVE-2016-6317
activerecord 4.2.3CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2015-7577, CVE-2016-6317
activerecord 4.2.2CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2015-7577, CVE-2016-6317
activerecord 4.2.1CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2015-7577, CVE-2016-6317
activerecord 4.2.0CVE-2025-55193, CVE-2022-44566, CVE-2022-32224, CVE-2015-7577, CVE-2016-6317

Which of your client projects are still on activerecord 4.2?

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

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