Is rails 3.2 vulnerable?

RubyGems · 28 releases from 3.2.0 to 3.2.22.5 · latest rails is 8.1.4.1 · checked 18 Nov 2026

No known advisories in the last release

rails 3.2.22.5, the last 3.2 release, has no known advisories. 1 advisory affects earlier 3.2.x releases, so update to 3.2.22.5.

Update within 3.2:bundle update --conservative rails # Gemfile: '>= 3.2.22.5'

Is your project on an affected rails?

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 3.2.x, affecting earlier releases

  • MediumCVE-2014-0081GHSA-m46p-ggm5-5j8324 Oct 2017

    Rails vulnerable to Cross-site Scripting

    Affected
    >=3.0.0 <3.2.17 · >=4.0.0 <4.0.3
    Fixed in
    3.2.17, 4.0.3

Every rails 3.2.x release

Affected: 3.2.0 to 3.2.16. 3.2.17 and later are not affected. Latest rails: 8.1.4.1.

VersionKnown advisories
rails 3.2.22.5None
rails 3.2.22.4None
rails 3.2.22.3None
rails 3.2.22.2None
rails 3.2.22.1None
rails 3.2.22None
rails 3.2.21None
rails 3.2.20None
rails 3.2.19None
rails 3.2.18None
rails 3.2.17None
rails 3.2.16CVE-2014-0081
rails 3.2.15CVE-2014-0081
rails 3.2.14CVE-2014-0081
rails 3.2.13CVE-2014-0081
rails 3.2.12CVE-2014-0081
rails 3.2.11CVE-2014-0081
rails 3.2.10CVE-2014-0081
rails 3.2.9CVE-2014-0081
rails 3.2.8CVE-2014-0081
rails 3.2.7CVE-2014-0081
rails 3.2.6CVE-2014-0081
rails 3.2.5CVE-2014-0081
rails 3.2.4CVE-2014-0081
rails 3.2.3CVE-2014-0081
rails 3.2.2CVE-2014-0081
rails 3.2.1CVE-2014-0081
rails 3.2.0CVE-2014-0081

Which of your client projects are still on rails 3.2?

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

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