VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

rails: vulnerability history, versions and safety

rails is a package in the Debian ecosystem. Vulert records 207 vulnerabilities for it across 70 releases, from Aug 2006 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
207 vulnerabilities recorded U207
i
35 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
12 in the last 12 months

Most recent disclosure 30 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rails vulnerabilities

Vulert verdict on rails i

Updated on 23 Oct 2026

Careful: 35 of the 207 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 207 vulnerabilities on record across 19 years, 12 in the last year.

What to do: Plan around the 35 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 207 over 19 years · 12 in the last year i
  • Latest disclosure 30 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 35 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for rails, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2:7.2.3.1+dfsg-1 U1 No Details →
2:7.2.3+dfsg-3 U10 No Details →
2:7.2.3+dfsg-2 U10 No Details →
2:7.2.3+dfsg-1 U10 No Details →
2:7.2.2.2+dfsg-2 U10 No Details →
2:7.2.2.2+dfsg-2~deb13u1 U10 No Details →
2:7.2.2.2+dfsg-1 U17 No Details →
2:7.2.2.1+dfsg-7 U35 No Details →
2:7.2.2.1+dfsg-6 U35 No Details →
2:7.2.2.1+dfsg-5 U35 No Details →
2:7.2.2.1+dfsg-4 U35 No Details →
2:7.2.2.1+dfsg-3 U35 No Details →
2:7.2.2.1+dfsg-2 U35 No Details →
2:7.2.2.1+dfsg-1 U35 No Details →
2:7.2.2.1+dfsg-1~exp6 U35 No Details →
2:7.2.2.1+dfsg-1~exp4 U35 No Details →
2:7.2.2.1+dfsg-1~exp3 U35 No Details →
2:7.2.2.1+dfsg-1~exp2 U35 No Details →
2:7.2.2.1+dfsg-1~exp1 U35 No Details →
2:6.1.7.10+dfsg-1~deb12u2 U10 No Details →
2:6.1.7.10+dfsg-1~deb12u1 U35 No Details →
2:6.1.7.3+dfsg-13 U35 No Details →
2:6.1.7.3+dfsg-12 U35 No Details →
2:6.1.7.3+dfsg-11 U35 No Details →
2:6.1.7.3+dfsg-10 U35 No Details →
2:6.1.7.3+dfsg-9 U35 No Details →
2:6.1.7.3+dfsg-8 U35 No Details →
2:6.1.7.3+dfsg-7 U35 No Details →
2:6.1.7.3+dfsg-7~exp1 U35 No Details →
2:6.1.7.3+dfsg-6 U35 No Details →
2:6.1.7.3+dfsg-5 U35 No Details →
2:6.1.7.3+dfsg-4 U35 No Details →
2:6.1.7.3+dfsg-3 U35 No Details →
2:6.1.7.3+dfsg-2 U35 No Details →
2:6.1.7.3+dfsg-2~deb12u1 U35 No Details →
2:6.1.7.3+dfsg-1 U35 No Details →
2:6.1.7.3+dfsg-1~bpo11+1 U35 No Details →
2:6.1.7+dfsg-3 U35 No Details →
2:6.1.7+dfsg-3~bpo11+2 U35 No Details →
2:6.1.7+dfsg-3~bpo11+1 U35 No Details →
2:6.1.7+dfsg-2 U35 No Details →
2:6.1.7+dfsg-1 U35 No Details →
2:6.1.6.1+dfsg-4 U35 No Details →
2:6.1.6.1+dfsg-3 U35 No Details →
2:6.1.6.1+dfsg-2 U35 No Details →
2:6.1.6.1+dfsg-1 U35 No Details →
2:6.1.4.7+dfsg-2 U35 No Details →
2:6.1.4.7+dfsg-1 U35 No Details →
2:6.1.4.6+dfsg-3 U35 No Details →
2:6.1.4.6+dfsg-2 U35 No Details →
2:6.1.4.6+dfsg-1 U35 No Details →
2:6.1.4.1+dfsg-8 U35 No Details →
2:6.1.4.1+dfsg-7 U35 No Details →
2:6.1.4.1+dfsg-6 U35 No Details →
2:6.1.4.1+dfsg-5 U35 No Details →
2:6.1.4.1+dfsg-4 U35 No Details →
2:6.1.4.1+dfsg-3 U35 No Details →
2:6.1.4.1+dfsg-2 U35 No Details →
2:6.1.4.1+dfsg-1 U35 No Details →
2:6.1.4+dfsg-4 U35 No Details →
2:6.1.4+dfsg-3 U35 No Details →
2:6.1.4+dfsg-2 U35 No Details →
2:6.1.4+dfsg-1 U35 No Details →
2:6.0.3.7+dfsg-3 U35 No Details →
2:6.0.3.7+dfsg-2 U63 No Details →
2:6.0.3.7+dfsg-2+deb11u5 U1 No Details →
2:6.0.3.7+dfsg-2+deb11u4 U10 No Details →
2:6.0.3.7+dfsg-2+deb11u3 U11 No Details →
2:6.0.3.7+dfsg-2+deb11u2 U37 No Details →
2:6.0.3.7+dfsg-2+deb11u1 U42 No Details →

Newest 70 of 70 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2006 4
  • 2007 8
  • 2008 4
  • 2009 10
  • 2011 14
  • 2012 8
  • 2013 22
  • 2014 14
  • 2015 4
  • 2016 20
  • 2017 8
  • 2018 4
  • 2019 8
  • 2020 16
  • 2021 14
  • 2022 13
  • 2023 11
  • 2024 6
  • 2025 9
  • 2026 10

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 12 of the 207 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for rails

The 5 most severe of 207 vulnerabilities recorded for this package

Search all 207 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Deserialization Vulnerability in Rails Package 9.8 critical 2:5.2.4.3+dfsg-1 19 Jun 2020
Remote Code Execution Vulnerability in Rails Package: CVE-2019-5420 9.8 critical 2:5.2.2.1+dfsg-1 27 Mar 2019
Critical Code Injection Vulnerability in Active Storage of Rails Package 9.8 critical 2:6.0.3.7+dfsg-2+deb11u1 26 May 2022
Authentication Bypass Vulnerability in Ruby on Rails (CVE-2009-2422) 9.8 critical 2.3.5-1 10 Jul 2009
Critical RCE Escalation Vulnerability in Rails Package Affecting YAML Serialized Columns 9.8 critical No fix published 05 Dec 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About rails

Is rails safe to use?

Vulert records 207 vulnerabilities for rails in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 207 not yet rated. 35 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does rails have?

207 vulnerabilities are recorded for rails in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 207 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rails vulnerabilities disclosed?

12 vulnerabilities were recorded for rails in the last 12 months, and the oldest entry in this database dates to 14 Aug 2006. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of rails are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor rails for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rails version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.