VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

rake: vulnerability history, versions and safety

rake is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 79 releases, first recorded in Feb 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rake vulnerabilities

Vulert verdict on rake 13.4.2 i

Updated on 23 Oct 2026

Good news: 13.4.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 13.4.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 13.4.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 13.4.2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 28 Feb 2020 i
  • Highest CVSS 6.4 i
  • With no published fix 0 i
  • Stars 2,465 i
  • OpenSSF scorecard 4/10 i
  • Last release 6 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for rake, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
13.4.2 16 Apr 2026 none MIT — Details →
13.4.1 14 Apr 2026 none MIT — Details →
13.4.0 14 Apr 2026 none MIT — Details →
13.3.1 29 Oct 2025 none MIT — Details →
13.3.0 30 May 2025 none MIT — Details →
13.2.1 05 Apr 2024 none MIT — Details →
13.2.0 02 Apr 2024 none MIT — Details →
13.1.0 28 Oct 2023 none MIT — Details →
13.0.6 09 Jul 2021 none MIT — Details →
13.0.5 08 Jul 2021 none MIT — Details →
13.0.4 06 Jul 2021 none MIT — Details →
13.0.3 21 Dec 2020 none MIT — Details →
13.0.2 19 Dec 2020 none MIT — Details →
13.0.1 12 Nov 2019 none MIT — Details →
13.0.0 27 Sep 2019 none MIT — Details →
13.0.0.pre.1 09 Sep 2019 none MIT — Details →
12.3.3 22 Jul 2019 none MIT — Details →
12.3.2 07 Dec 2018 M1 MIT Yes Details →
12.3.1 22 Mar 2018 M1 MIT Yes Details →
12.3.0 15 Nov 2017 M1 MIT Yes Details →
12.2.1 25 Oct 2017 M1 MIT Yes Details →
12.2.0 25 Oct 2017 M1 MIT Yes Details →
12.1.0 11 Sep 2017 M1 MIT Yes Details →
12.0.0 06 Dec 2016 M1 MIT Yes Details →
12.0.0.beta1 02 Dec 2016 M1 MIT Yes Details →
11.3.0 20 Sep 2016 M1 MIT Yes Details →
11.2.2 12 Jun 2016 M1 MIT Yes Details →
11.2.0 11 Jun 2016 M1 MIT Yes Details →
11.1.2 27 Mar 2016 M1 MIT Yes Details →
11.1.1 14 Mar 2016 M1 MIT Yes Details →
11.1.0 11 Mar 2016 M1 MIT Yes Details →
11.0.1 09 Mar 2016 M1 MIT Yes Details →
10.5.0 13 Jan 2016 M1 MIT Yes Details →
10.4.2 03 Dec 2014 M1 MIT Yes Details →
10.4.1 02 Dec 2014 M1 MIT Yes Details →
10.4.0 25 Nov 2014 M1 MIT Yes Details →
10.3.2 16 May 2014 M1 MIT Yes Details →
10.3.1 17 Apr 2014 M1 MIT Yes Details →
10.3.0 15 Apr 2014 M1 MIT Yes Details →
10.2.2 27 Mar 2014 M1 MIT Yes Details →
10.2.1 25 Mar 2014 M1 MIT Yes Details →
10.2.0 24 Mar 2014 M1 MIT Yes Details →
10.1.1 20 Dec 2013 M1 MIT Yes Details →
10.1.0 20 Jun 2013 M1 MIT Yes Details →
10.1.0.beta.3 30 Apr 2013 M1 MIT Yes Details →
10.1.0.beta.2 30 Apr 2013 M1 MIT Yes Details →
10.1.0.beta.1 26 Apr 2013 M1 MIT Yes Details →
10.0.4 25 Mar 2013 M1 MIT Yes Details →
10.0.3 12 Dec 2012 M1 — Yes Details →
0.9.6 12 Dec 2012 M1 — Yes Details →
10.0.2 19 Nov 2012 M1 — Yes Details →
0.9.5 19 Nov 2012 M1 — Yes Details →
10.0.1 14 Nov 2012 M1 — Yes Details →
0.9.4 14 Nov 2012 M1 — Yes Details →
10.0.0 12 Nov 2012 M1 — Yes Details →
0.9.3 12 Nov 2012 M1 — Yes Details →
0.9.3.beta.4 09 Nov 2012 M1 — Yes Details →
10.0.0.beta.2 26 Oct 2012 M1 — Yes Details →
10.0.0.beta.1 25 Oct 2012 M1 — Yes Details →
0.9.3.beta.3 25 Oct 2012 M1 — Yes Details →
0.9.3.beta.2 22 Oct 2012 M1 — Yes Details →
0.9.2.2 22 Oct 2011 M1 — Yes Details →
0.9.3.beta.1 06 Aug 2011 M1 — Yes Details →
0.9.2 05 Jun 2011 M1 — Yes Details →
0.9.1 01 Jun 2011 M1 — Yes Details →
0.9.0 20 May 2011 M1 — Yes Details →
0.9.0.beta.5 14 Mar 2011 M1 — Yes Details →
0.9.0.beta.4 06 Mar 2011 M1 — Yes Details →
0.9.0.beta.2 05 Mar 2011 M1 — Yes Details →
0.9.0.beta.1 28 Feb 2011 M1 — Yes Details →
0.9.0.beta.0 23 Feb 2011 M1 — Yes Details →
0.4.10 25 Jul 2009 M1 — Yes Details →
0.4.11 25 Jul 2009 M1 — Yes Details →
0.4.12 25 Jul 2009 M1 — Yes Details →
0.4.13 25 Jul 2009 M1 — Yes Details →
0.4.14 25 Jul 2009 M1 — Yes Details →
0.4.15 25 Jul 2009 M1 — Yes Details →
0.4.8 25 Jul 2009 M1 — Yes Details →
0.4.9 25 Jul 2009 M1 — Yes Details →
0.5.0 25 Jul 2009 M1 — Yes Details →
0.5.3 25 Jul 2009 M1 — Yes Details →
0.5.4 25 Jul 2009 M1 — Yes Details →
0.6.0 25 Jul 2009 M1 — Yes Details →
0.6.2 25 Jul 2009 M1 — Yes Details →
0.7.0 25 Jul 2009 M1 — Yes Details →
0.7.1 25 Jul 2009 M1 — Yes Details →
0.7.2 25 Jul 2009 M1 — Yes Details →
0.7.3 25 Jul 2009 M1 — Yes Details →
0.8.0 25 Jul 2009 M1 — Yes Details →
0.8.1 25 Jul 2009 M1 — Yes Details →
0.8.2 25 Jul 2009 M1 — Yes Details →
0.8.3 25 Jul 2009 M1 — Yes Details →
0.8.4 25 Jul 2009 M1 — Yes Details →
0.8.5 25 Jul 2009 M1 — Yes Details →
0.8.6 25 Jul 2009 M1 — Yes Details →
0.8.7 25 Jul 2009 M1 — Yes Details →

All 96 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for rake

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-8130: OS Command Injection in Rake 6.4 medium 12.3.3 28 Feb 2020

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 rake

Is rake safe to use?

Vulert records 1 vulnerabilities for rake in RubyGems: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is rake's Vulert package health score?

Vulert scores rake 83/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of rake affected?

No. 13.4.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of rake should I use?

13.4.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does rake have?

1 vulnerability is recorded for rake in the RubyGems ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rake vulnerabilities disclosed?

0 vulnerabilities were recorded for rake in the last 12 months, and the oldest entry in this database dates to 28 Feb 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 rake 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 rake for upcoming vulnerabilities?

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