VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

rest-client: vulnerability history, versions and safety

rest-client is a package in the RubyGems ecosystem. Vulert records 3 vulnerabilities for it across 52 releases, from Oct 2017 to Aug 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C2 L1
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 rest-client vulnerabilities

Vulert verdict on rest-client 2.1.0 i

Updated on 23 Oct 2026

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

Package health score 63/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 2.1.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 20 Aug 2019 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 5,212 i
  • OpenSSF scorecard 1/10 i
  • Last release 86 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 rest-client, 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
2.1.0 21 Aug 2019 none MIT — Details →
1.6.14 21 Aug 2019 C2 L1 MIT Yes Details →
2.1.0.rc1 05 Jul 2017 none MIT — Details →
2.0.2 23 Apr 2017 none MIT — Details →
2.0.1 19 Feb 2017 none MIT — Details →
2.0.0 02 Jul 2016 none MIT — Details →
2.0.0.rc4 19 Jun 2016 none MIT — Details →
2.0.0.rc3 06 Jun 2016 none MIT — Details →
2.0.0.rc2 13 Sep 2015 none MIT — Details →
1.6.9 10 Jun 2015 C1 L1 MIT Yes Details →
2.0.0.rc1 10 Jun 2015 none MIT — Details →
1.8.0 24 Mar 2015 none MIT — Details →
1.8.0.rc1 23 Mar 2015 C1 MIT Yes Details →
1.7.3 20 Feb 2015 C1 MIT Yes Details →
1.7.2 14 Jul 2014 C1 L1 MIT Yes Details →
1.7.2.rc1 13 Jul 2014 C1 L1 MIT Yes Details →
1.7.1 09 Jul 2014 C1 L1 MIT Yes Details →
1.7.0 08 Jul 2014 C1 L1 MIT Yes Details →
1.6.8 08 Jul 2014 C1 L1 MIT Yes Details →
1.7.0.rc1 01 May 2014 C2 L1 MIT Yes Details →
1.6.8.rc1 01 May 2014 C1 L1 MIT Yes Details →
1.6.7 24 Aug 2011 C1 L1 — Yes Details →
1.6.6 22 Aug 2011 C1 L1 — Yes Details →
1.6.5 22 Aug 2011 C1 L1 — Yes Details →
1.6.3 04 Jun 2011 C1 L1 — Yes Details →
1.6.2.a 13 Feb 2011 C1 L1 — Yes Details →
1.6.1 29 Aug 2010 C1 L1 — Yes Details →
1.6.1.a 24 Jul 2010 C1 L1 — Yes Details →
1.6.0 02 Jul 2010 L1 — Yes Details →
1.6.0.a 28 Jun 2010 L1 — Yes Details →
1.5.1 16 May 2010 L1 — Yes Details →
1.5.0 30 Apr 2010 L1 — Yes Details →
1.5.0.b 23 Apr 2010 L1 — Yes Details →
1.5.0.a 23 Apr 2010 L1 — Yes Details →
1.4.2 13 Mar 2010 L1 — Yes Details →
1.4.1 05 Mar 2010 L1 — Yes Details →
1.4.0 28 Feb 2010 L1 — Yes Details →
1.4.0.a 22 Feb 2010 L1 — Yes Details →
1.3.1 10 Feb 2010 L1 — Yes Details →
1.3.0 29 Jan 2010 L1 — Yes Details →
1.2.0 03 Jan 2010 L1 — Yes Details →
1.1.0 31 Dec 2009 L1 — Yes Details →
1.0.4 12 Dec 2009 L1 — Yes Details →
1.0.2 05 Aug 2009 L1 — Yes Details →
1.0.3 05 Aug 2009 L1 — Yes Details →
0.1 25 Jul 2009 L1 — Yes Details →
0.2 25 Jul 2009 L1 — Yes Details →
0.3 25 Jul 2009 L1 — Yes Details →
0.4 25 Jul 2009 L1 — Yes Details →
0.5 25 Jul 2009 L1 — Yes Details →
0.5.1 25 Jul 2009 L1 — Yes Details →
0.6 25 Jul 2009 L1 — Yes Details →
0.6.1 25 Jul 2009 L1 — Yes Details →
0.6.2 25 Jul 2009 L1 — Yes Details →
0.7 25 Jul 2009 L1 — Yes Details →
0.8 25 Jul 2009 L1 — Yes Details →
0.8.1 25 Jul 2009 L1 — Yes Details →
0.8.2 25 Jul 2009 L1 — Yes Details →
0.9 25 Jul 2009 L1 — Yes Details →
0.9.2 25 Jul 2009 L1 — Yes Details →
1.0 25 Jul 2009 L1 — Yes Details →
1.0.1 25 Jul 2009 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 1
  • 2019 1

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

03 Vulnerabilities

Recorded vulnerabilities for rest-client

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-15224: Backdoor/Malicious code in rest-client gem 9.8 critical 1.7.0 20 Aug 2019
CVE-2015-1820: Session Fixation Vulnerability in rest-client 9.8 critical 1.8.0 13 Aug 2018
CVE-2015-3448: rest-client Local Information Disclosure N/A low 1.7.3 24 Oct 2017

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 rest-client

Is rest-client safe to use?

Vulert records 3 vulnerabilities for rest-client in RubyGems: 2 critical, 0 high, 0 medium and 1 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 rest-client's Vulert package health score?

Vulert scores rest-client 63/100, which reads as usable, but worth attention. 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 rest-client affected?

No. 2.1.0, 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 rest-client should I use?

2.1.0 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 rest-client have?

3 vulnerabilities are recorded for rest-client in the RubyGems ecosystem: 2 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rest-client vulnerabilities disclosed?

0 vulnerabilities were recorded for rest-client in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 rest-client 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 rest-client for upcoming vulnerabilities?

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