RUBY ON RAILS COVERAGE
Rails 8.0 and 7.2 are out of support. Your patching does not have to be.
Ruby on Rails extended support from OSSeva covers the Rails versions the Rails team no longer fixes. Rails 8.0 security support ended on 7 November 2026 and Rails 7.2 on 9 August 2026, and the Rails maintenance page now lists only 8.1 as supported. Send your work email and an engineer replies within 1 business day with coverage for your Rails version.
| Who it is for | Teams running Rails 7.2 or 8.0 whose upgrade to 8.1 is blocked by gem compatibility, a Ruby upgrade or a release freeze |
|---|---|
| What you get | Signed patched Rails gems on your line, with the public API, your Gemfile.lock constraints and Active Storage behaviour unchanged. Assure adds an exposure audit, an upgrade path assessment and 24/7 reactive support. |
| How it is priced | Per application. Ask for a quote. |
| What happens next | You send your work email, we confirm your Rails and Ruby versions and which Rails components you use, and you get a coverage plan. |
Reply within 1 business day · No commitment · or book a 15-minute call
Last reviewed
Trusted globally by enterprises





Rails support dates, read on 19 November 2026
Rails separates bug fixes from security fixes: a minor release gets bug fixes for one year and security fixes for two years after its first release. Dates for 8.1 and 8.0 are from the Rails maintenance page; 7.2 is no longer listed there, so its date is from the policy formula and endoflife.date.
| Series | Released | Bug fixes until | Security fixes until | Needs Ruby |
|---|---|---|---|---|
| 7.2 | 9 Aug 2024 | 9 Aug 2025 | 9 Aug 2026 | 3.1.0 or newer |
| 8.0 | 7 Nov 2024 | 7 May 2026 | 7 Nov 2026 | 3.2.0 or newer |
| 8.1 | 22 Oct 2025 | 10 Oct 2026 | 10 Oct 2027 | 3.2.0 or newer |
The maintenance page groups support into new features, bug fixes and security issues, with no separate category for severe security issues. Its dates for 8.0 and 8.1 do not follow the one-year and two-year formula to the day (8.0 bug fixes run to 7 May 2026), so the table gives the dates as the page lists them.
Ruby on Rails end-of-life dates for every series →rubyonrails.org: maintenance policy →
Rails vulnerabilities and which lines got a fix
Rails shipped fixes for the first CVE below on 7.2, 8.0 and 8.1 while 7.2 was still supported. The next two were fixed on 8.1 and 8.0 only: the Rails advisories give the affected range as every release before 8.0.5.2, which includes 7.2, and no 7.2 release carries the fix.
| CVE | Issue | Severity | Fixed in |
|---|---|---|---|
| CVE-2026-66066 | Arbitrary file read and remote code execution in Active Storage variant processing (libvips) | Critical, CVSS 9.5 | 7.2.3.2, 8.0.5.1, 8.1.3.1 |
| CVE-2026-126186 | Arbitrary file read and remote code execution in Active Storage video previews, analysis and image processing | High, CVSS 8.8 | 8.0.5.2, 8.1.4.1. No 7.2 release. |
| CVE-2026-126081 | Strong Parameters bypass in Parameters#each_key (Action Pack) | High, CVSS 7.5 | 8.0.5.2, 8.1.4.1. No 7.2 release. |
Sources: the rails/rails GitHub security advisories GHSA-xr9x-r78c-5hrm, GHSA-v924-7rp8-4mxh and GHSA-wm3x-v3qw-4jh3, and the matching CVE records on cveawg.mitre.org. Rails 8.0.5.2, the last 8.0 security release, is dated 4 November 2026 on rubygems.org, three days before 8.0 support ended. Whether a given application is exposed depends on which Rails components it uses.
Why now
Rails 8.0 lost security support on 7 November 2026
The Rails maintenance page lists Rails 8.0 with bug fixes until 7 May 2026 and security fixes until 7 November 2026. Only 8.1 is still listed as supported. For an unsupported series the page tells users they are responsible for their own bug and security fixes.
Rails 7.2 ended on 9 August 2026 and is no longer listed
Rails gives each minor release one year of bug fixes and two years of security fixes. Rails 7.2 was first released on 9 August 2024, so its security window closed on 9 August 2026, per the policy and endoflife.date. The maintenance page now lists only 8.1 and 8.0.
A Ruby end of life sits under the Rails one
Rails 8.0 requires Ruby 3.2.0 or newer and Rails 7.2 requires Ruby 3.1.0 or newer, per the gem metadata on rubygems.org. Ruby 3.2 ended on 1 April 2026 and Ruby 3.1 on 26 March 2025, so an application on either Rails line is often on an ended Ruby too.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 7.2(Security support ended 9 Aug 2026) | EOL | Clean |
| 8.0(Security support ended 7 Nov 2026) | EOL | Clean |
| 8.1(Security support until 10 Oct 2027. Assessed case by case.) | Current | Clean |
Running a Ruby on Rails version or build not listed here?
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Security patches for Rails 8.0 and 7.2 after end of life.
- Backported security fixes for Rails 8.0 and 7.2
- Critical CVEs fixed within 48 hours, High within 7 days
- Signed artifacts (GPG + Sigstore)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus compliance documentation and upgrade planning.
- Everything in Patch
- SOC 2 / HIPAA attestation package
- Rails upgrade path assessment
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.
- Everything in Assure
- 24/7 application and runtime monitoring
- 15-minute P1 incident response SLA
- Named senior engineer on your account
All tiers priced per cluster/application — not per core.
Which Rails versions does OSSeva patch?
Ruby on Rails 8.0 and 7.2 after end of life. Other versions are assessed case by case through a version coverage check.
How fast are Rails vulnerabilities patched?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.
Do I need Ruby patched as well as Rails?
Often yes. Rails 8.0 needs Ruby 3.2 or newer and Rails 7.2 needs Ruby 3.1 or newer, and the Ruby core team has ended both 3.2 and 3.1. The interpreter and the framework are patched separately: see the Ruby page for the interpreter.
How is OSSeva Rails support priced?
It is priced per application. Request a quote and a senior engineer replies within 1 business day.
Get a quote
Ready to get Ruby on Rails patched and supported?
Tell us your Ruby on Rails versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?