VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

ruby2.7: vulnerability history, versions and safety

ruby2.7 is a package in the Debian ecosystem. Vulert records 45 vulnerabilities for it across 7 releases, from May 2020 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
45 vulnerabilities recorded U45
i
15 with no fix published

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

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

Most recent disclosure 22 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ruby2.7 vulnerabilities

Vulert verdict on ruby2.7 i

Updated on 23 Oct 2026

Careful: 15 of the 45 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 45 vulnerabilities on record across 6 years, 11 in the last year.

What to do: Plan around the 15 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 45 over 6 years · 11 in the last year i
  • Latest disclosure 22 Jun 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 15 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 ruby2.7, 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.5-1 U15 No Details →
2.7.4-1 U42 No Details →
2.7.4-1+deb11u5 U15 No Details →
2.7.4-1+deb11u4 U21 No Details →
2.7.4-1+deb11u3 U22 No Details →
2.7.4-1+deb11u2 U30 No Details →
2.7.4-1+deb11u1 U38 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 2
  • 2022 6
  • 2023 2
  • 2024 11
  • 2025 13
  • 2026 10

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

03 Vulnerabilities

Recorded vulnerabilities for ruby2.7

The 5 most severe of 45 vulnerabilities recorded for this package

Search all 45 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Code Execution Vulnerability in Ruby ERB Templating System 8.1 high No fix published 24 Apr 2026
Regular Expression Denial of Service in CGI Gem for Ruby - CVE-2025-27220 7.5 high 2.7.4-1+deb11u5 04 Mar 2025
ReDoS Vulnerability in Ruby URI Component: CVE-2023-36617 5.3 medium 2.7.4-1+deb11u2 29 Jun 2023
Authentication Credential Leakage in URI Gem for Ruby 5.3 medium 2.7.4-1+deb11u5 04 Mar 2025
Buffer Overflow Vulnerability in zlib Ruby Interface - Affected Packages: ruby2.7, ruby3.1, ruby3.3 N/A unrated No fix published 17 Apr 2026

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 ruby2.7

Is ruby2.7 safe to use?

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

How many vulnerabilities does ruby2.7 have?

45 vulnerabilities are recorded for ruby2.7 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 45 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 ruby2.7 vulnerabilities disclosed?

11 vulnerabilities were recorded for ruby2.7 in the last 12 months, and the oldest entry in this database dates to 04 May 2020. 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 ruby2.7 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 ruby2.7 for upcoming vulnerabilities?

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