VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

thin: vulnerability history, versions and safety

thin is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 21 releases, first recorded in Oct 2017. 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 H1
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 thin vulnerabilities

Vulert verdict on thin 2.0.1 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 2.0.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Oct 2017 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,276 i
  • OpenSSF scorecard 3/10 i
  • Last release 15 months ago i
  • Licence GPL-2.0-or-later 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 thin, 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.0.1 24 Jun 2025 none GPL-2.0-or-later — Details →
2.0.0 22 Jun 2025 none GPL-2.0+ — Details →
1.8.2 31 Mar 2023 none GPL-2.0+ — Details →
1.8.1 20 May 2021 none GPL-2.0+ — Details →
1.8.0 13 Nov 2020 none GPL-2.0+ — Details →
1.7.2 08 Jul 2017 none non-standard — Details →
1.7.1 13 Jun 2017 none non-standard — Details →
1.7.0 27 May 2016 none non-standard — Details →
1.6.4 19 Sep 2015 none non-standard — Details →
1.6.3 02 Oct 2014 none non-standard — Details →
1.6.2 04 Mar 2014 none Ruby — Details →
1.6.1 31 Oct 2013 none Ruby — Details →
1.6.0 02 Oct 2013 none Ruby — Details →
1.5.1 18 Mar 2013 none Ruby — Details →
1.5.0 22 Sep 2012 none — — Details →
1.4.1 03 Jul 2012 none — — Details →
1.4.0 03 Jul 2012 none — — Details →
1.3.1 14 Nov 2011 none — — Details →
1.3.0 12 Nov 2011 none — — Details →
1.2.11 28 Mar 2011 none — — Details →
1.2.10 24 Mar 2011 none — — Details →
1.2.9 23 Mar 2011 none — — Details →
1.2.8 25 Feb 2011 none — — Details →
1.2.7 01 Mar 2010 none — — Details →
1.2.6 25 Feb 2010 none — — Details →
1.2.5 05 Nov 2009 none — — Details →
1.2.4 24 Sep 2009 none — — Details →
1.2.3 24 Sep 2009 H1 — Yes Details →
0.3.0 25 Jul 2009 H1 — Yes Details →
0.4.0 25 Jul 2009 H1 — Yes Details →
0.4.1 25 Jul 2009 H1 — Yes Details →
0.5.0 25 Jul 2009 H1 — Yes Details →
0.5.2 25 Jul 2009 H1 — Yes Details →
0.5.3 25 Jul 2009 H1 — Yes Details →
0.5.4 25 Jul 2009 H1 — Yes Details →
0.6.0 25 Jul 2009 H1 — Yes Details →
0.6.1 25 Jul 2009 H1 — Yes Details →
0.6.2 25 Jul 2009 H1 — Yes Details →
0.6.3 25 Jul 2009 H1 — Yes Details →
0.6.4 25 Jul 2009 H1 — Yes Details →
0.7.0 25 Jul 2009 H1 — Yes Details →
0.7.1 25 Jul 2009 H1 — Yes Details →
0.8.0 25 Jul 2009 H1 — Yes Details →
0.8.1 25 Jul 2009 H1 — Yes Details →
0.8.2 25 Jul 2009 H1 — Yes Details →
1.0.0 25 Jul 2009 H1 — Yes Details →
1.2.1 25 Jul 2009 H1 — Yes Details →
1.2.2 25 Jul 2009 H1 — Yes Details →

All 48 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

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 thin

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2009-3287: Vulnerability in Thin web server allows IP address spoofing N/A high 1.2.4 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 thin

Is thin safe to use?

Vulert records 1 vulnerabilities for thin in RubyGems: 0 critical, 1 high, 0 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 thin's Vulert package health score?

Vulert scores thin 77/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 thin affected?

No. 2.0.1, 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 thin should I use?

2.0.1 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 thin have?

1 vulnerability is recorded for thin in the RubyGems ecosystem: 0 critical, 1 high, 0 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 thin vulnerabilities disclosed?

0 vulnerabilities were recorded for thin 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 thin 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 thin for upcoming vulnerabilities?

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