VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

sinatra: vulnerability history, versions and safety

sinatra is a package in the RubyGems ecosystem. Vulert records 7 vulnerabilities for it across 108 releases, from Feb 2018 to Oct 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H2 M4 L1
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 sinatra vulnerabilities

Vulert verdict on sinatra 4.2.1 i

Updated on 23 Oct 2026

Careful: 4.2.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.2.1 — affected i
  • Vulnerabilities on record 7 over 7 years · 0 in the last year i
  • Latest disclosure 10 Oct 2025 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Stars 12,454 i
  • OpenSSF scorecard 4/10 i
  • Last release 12 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 sinatra, 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
4.2.1 10 Oct 2025 M1 MIT No Details →
4.2.0 08 Oct 2025 M1 MIT No Details →
4.0.1 23 May 2025 L1 MIT Yes Details →
4.1.1 20 Nov 2024 L1 MIT Yes Details →
4.1.0 18 Nov 2024 L1 MIT Yes Details →
4.0.0 19 Jan 2024 M2 L1 MIT No Details →
3.2.0 29 Dec 2023 M2 L1 MIT No Details →
3.1.0 07 Aug 2023 M2 L1 MIT No Details →
3.0.6 11 Apr 2023 M2 L1 MIT No Details →
3.0.5 16 Dec 2022 M2 L1 MIT No Details →
2.2.4 16 Dec 2022 M2 L1 MIT No Details →
2.2.3 25 Nov 2022 M2 L1 MIT No Details →
3.0.4 25 Nov 2022 M2 L1 MIT No Details →
3.0.3 11 Nov 2022 H1 M2 L1 MIT No Details →
3.0.2 01 Oct 2022 H1 M2 L1 MIT No Details →
3.0.1 26 Sep 2022 H1 M2 L1 MIT No Details →
3.0.0 26 Sep 2022 H1 M2 L1 MIT No Details →
2.2.2 23 Jul 2022 M2 L1 MIT No Details →
2.2.1 15 Jul 2022 M2 L1 MIT No Details →
2.2.0 15 Feb 2022 M2 L1 MIT No Details →
2.1.0 04 Sep 2020 H1 M2 L1 MIT No Details →
2.0.8.1 01 Jan 2020 H1 M2 L1 MIT No Details →
2.0.8 01 Jan 2020 H1 M2 L1 MIT No Details →
2.0.7 22 Aug 2019 H1 M2 L1 MIT No Details →
2.0.6 21 Aug 2019 H1 M2 L1 MIT No Details →
2.0.5 22 Dec 2018 H1 M2 L1 MIT No Details →
2.0.4 15 Sep 2018 H1 M2 L1 MIT No Details →
2.0.3 08 Jun 2018 H1 M2 L1 MIT No Details →
2.0.2 05 Jun 2018 H1 M2 L1 MIT No Details →
2.0.1 16 Feb 2018 H1 M3 L1 MIT No Details →
2.0.1.rc1 13 Feb 2018 H1 M4 L1 MIT No Details →
2.0.0 07 May 2017 H1 M4 L1 MIT No Details →
2.0.0.rc6 06 May 2017 H1 M3 L1 MIT No Details →
2.0.0.rc5 06 May 2017 H1 M3 L1 MIT No Details →
2.0.0.rc2 19 Mar 2017 H1 M3 L1 MIT No Details →
2.0.0.rc1 04 Mar 2017 H1 M3 L1 MIT No Details →
1.4.8 30 Jan 2017 H1 M2 L1 MIT No Details →
2.0.0.beta2 22 Aug 2016 H1 M3 L1 MIT No Details →
2.0.0.beta1 22 Aug 2016 H1 M3 L1 MIT No Details →
1.4.7 24 Jan 2016 H1 M2 L1 MIT No Details →
1.4.6 24 Mar 2015 H1 M2 L1 MIT No Details →
1.4.5 08 Apr 2014 H1 M2 L1 MIT No Details →
1.4.4 21 Oct 2013 H1 M2 L1 — No Details →
1.4.3 07 Jun 2013 H1 M2 L1 — No Details →
1.4.2 21 Mar 2013 H1 M2 L1 — No Details →
1.4.1 15 Mar 2013 H1 M2 L1 — No Details →
1.4.0 15 Mar 2013 H1 M2 L1 — No Details →
1.3.6 15 Mar 2013 H1 M2 L1 — No Details →
1.2.9 15 Mar 2013 H1 M2 L1 — No Details →
1.4.0.d 09 Mar 2013 H1 M2 L1 — No Details →
1.4.0.c 26 Feb 2013 H1 M2 L1 — No Details →
1.4.0.b 26 Feb 2013 H1 M2 L1 — No Details →
1.4.0.a 26 Feb 2013 H1 M2 L1 — No Details →
1.3.5 25 Feb 2013 H1 M2 L1 — No Details →
1.3.4 26 Jan 2013 H1 M2 L1 — No Details →
1.3.3 19 Aug 2012 H1 M2 L1 — No Details →
1.3.2 30 Dec 2011 H1 M2 L1 — No Details →
1.2.8 30 Dec 2011 H1 M2 L1 — No Details →
1.3.1 05 Oct 2011 H1 M2 L1 — No Details →
1.2.7 01 Oct 2011 H1 M2 L1 — No Details →
1.3.0 01 Oct 2011 H1 M2 L1 — No Details →
1.3.0.g 25 Sep 2011 H1 M2 L1 — No Details →
1.3.0.f 11 Sep 2011 H1 M2 L1 — No Details →
1.3.0.e 09 Jun 2011 H1 M2 L1 — No Details →
1.2.6 01 May 2011 H1 M2 L1 — No Details →
1.3.0.d 30 Apr 2011 H1 M2 L1 — No Details →
1.3.0.c 13 Apr 2011 H1 M2 L1 — No Details →
1.2.3 13 Apr 2011 H1 M2 L1 — No Details →
1.1.4 13 Apr 2011 H1 M2 L1 — No Details →
1.2.2 08 Apr 2011 H1 M2 L1 — No Details →
1.3.0.b 08 Apr 2011 H1 M2 L1 — No Details →
1.3.0.a 22 Mar 2011 H1 M2 L1 — No Details →
1.2.1 17 Mar 2011 H1 M2 L1 — No Details →
1.2.0 03 Mar 2011 H1 M2 L1 — No Details →
1.2.0.d 26 Feb 2011 H1 M2 L1 — No Details →
1.1.3 20 Feb 2011 H1 M2 L1 — No Details →
1.2.0.c 19 Feb 2011 H1 M2 L1 — No Details →
1.1.2 25 Dec 2010 H1 M2 L1 — No Details →
1.2.0.a 25 Dec 2010 H1 M2 L1 — No Details →
1.1.0 24 Oct 2010 H1 M2 L1 — No Details →
1.1.b 23 Oct 2010 H1 M2 L1 — No Details →
1.1.a 19 Oct 2010 H1 M2 L1 — No Details →
1.0 23 Mar 2010 H1 M2 L1 — No Details →
1.0.b 07 Mar 2010 H1 M2 L1 — No Details →
0.9.6 07 Mar 2010 H1 M2 L1 — No Details →
0.9.5 04 Mar 2010 H1 M2 L1 — No Details →
1.0.a 28 Jan 2010 H1 M2 L1 — No Details →
0.9.4 05 Aug 2009 H1 M2 L1 — No Details →
0.1.0 25 Jul 2009 H1 M2 L1 — No Details →
0.1.5 25 Jul 2009 H1 M2 L1 — No Details →
0.1.6 25 Jul 2009 H1 M2 L1 — No Details →
0.1.7 25 Jul 2009 H1 M2 L1 — No Details →
0.2.0 25 Jul 2009 H1 M2 L1 — No Details →
0.2.1 25 Jul 2009 H1 M2 L1 — No Details →
0.2.2 25 Jul 2009 H1 M2 L1 — No Details →
0.3.0 25 Jul 2009 H1 M2 L1 — No Details →
0.3.1 25 Jul 2009 H1 M2 L1 — No Details →
0.3.2 25 Jul 2009 H1 M2 L1 — No Details →
0.3.3 25 Jul 2009 H1 M2 L1 — No Details →
0.9.0 25 Jul 2009 H1 M2 L1 — No Details →
0.9.0.1 25 Jul 2009 H1 M2 L1 — No Details →
0.9.0.2 25 Jul 2009 H1 M2 L1 — No Details →
0.9.0.3 25 Jul 2009 H1 M2 L1 — No Details →
0.9.0.4 25 Jul 2009 H1 M2 L1 — No Details →
0.9.0.5 25 Jul 2009 H1 M2 L1 — No Details →
0.9.1 25 Jul 2009 H1 M2 L1 — No Details →
0.9.1.1 25 Jul 2009 H1 M2 L1 — No Details →
0.9.2 25 Jul 2009 H1 M2 L1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2022 2
  • 2024 2
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for sinatra

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Sinatra vulnerable to Reflected File Download attack 8.8 high 3.0.4 30 Nov 2022
CVE-2022-29970: Vulnerability in Sinatra 7.5 high 2.2.0 03 May 2022
CVE-2018-11627: Sinatra Cross-site Scripting vulnerability 6.1 medium 2.0.2 05 Jun 2018
CVE-2024-21510: Sinatra Open Redirect Vulnerability via X-Forwarded-Host Header 5.4 medium No fix published 01 Nov 2024
CVE-2024-21510: Sinatra Open Redirect Vulnerability via X-Forwarded-Host Header 5.4 medium 4.1.0 01 Nov 2024

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 sinatra

Is sinatra safe to use?

Vulert records 7 vulnerabilities for sinatra in RubyGems: 0 critical, 2 high, 4 medium and 1 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is sinatra's Vulert package health score?

Vulert scores sinatra 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of sinatra affected?

Yes. 4.2.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of sinatra should I use?

4.2.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 sinatra have?

7 vulnerabilities are recorded for sinatra in the RubyGems ecosystem: 0 critical, 2 high, 4 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 sinatra vulnerabilities disclosed?

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

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