VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

sqlite3: vulnerability history, versions and safety

sqlite3 is a package in the RubyGems ecosystem. Vulert records 2 vulnerabilities for it across 60 releases, from Oct 2022 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 02 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sqlite3 vulnerabilities

Vulert verdict on sqlite3 2.10.1 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 2.10.1 — unaffected i
  • Vulnerabilities on record 2 over 3 years · 1 in the last year i
  • Latest disclosure 02 Oct 2026 i
  • Highest CVSS 6.3 i
  • With no published fix 0 i
  • Stars 845 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence BSD-3-Clause 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 sqlite3, 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.10.1 19 Oct 2026 none BSD-3-Clause — Details →
2.10.0 13 Oct 2026 none BSD-3-Clause — Details →
2.9.6 11 Aug 2026 none BSD-3-Clause — Details →
2.9.5 07 Jun 2026 M1 BSD-3-Clause Yes Details →
2.9.4 06 May 2026 M1 BSD-3-Clause Yes Details →
2.9.3 15 Apr 2026 M1 BSD-3-Clause Yes Details →
2.9.2 15 Mar 2026 M1 BSD-3-Clause Yes Details →
2.9.2.rc2 15 Mar 2026 M1 BSD-3-Clause Yes Details →
2.9.1 28 Feb 2026 M1 BSD-3-Clause Yes Details →
2.9.0 27 Dec 2025 M1 BSD-3-Clause Yes Details →
2.8.1 29 Nov 2025 M1 BSD-3-Clause Yes Details →
2.8.0 05 Nov 2025 M1 BSD-3-Clause Yes Details →
2.7.4 19 Sep 2025 M1 BSD-3-Clause Yes Details →
2.7.3 18 Jul 2025 M1 BSD-3-Clause Yes Details →
2.7.2 05 Jul 2025 M1 BSD-3-Clause Yes Details →
2.7.1 30 Jun 2025 M1 BSD-3-Clause Yes Details →
2.7.0 09 Jun 2025 M1 BSD-3-Clause Yes Details →
2.6.0 20 Feb 2025 M1 BSD-3-Clause Yes Details →
2.5.0 25 Dec 2024 M1 BSD-3-Clause Yes Details →
2.5.0.rc1 14 Dec 2024 M1 BSD-3-Clause Yes Details →
2.4.1 08 Dec 2024 M1 BSD-3-Clause Yes Details →
2.4.0 03 Dec 2024 M1 BSD-3-Clause Yes Details →
2.3.1 25 Nov 2024 M1 BSD-3-Clause Yes Details →
2.3.0 20 Nov 2024 M1 BSD-3-Clause Yes Details →
2.2.0 30 Oct 2024 M1 BSD-3-Clause Yes Details →
2.1.1 22 Oct 2024 M1 BSD-3-Clause Yes Details →
2.1.0 24 Sep 2024 M1 BSD-3-Clause Yes Details →
2.1.0.rc3 24 Sep 2024 M1 BSD-3-Clause Yes Details →
2.1.0.rc2 19 Sep 2024 M1 BSD-3-Clause Yes Details →
2.0.4 13 Aug 2024 M1 BSD-3-Clause Yes Details →
2.0.3 29 Jul 2024 M1 BSD-3-Clause Yes Details →
2.0.2 23 May 2024 M1 BSD-3-Clause Yes Details →
2.0.1 20 Apr 2024 M1 BSD-3-Clause Yes Details →
2.0.0 17 Apr 2024 M1 BSD-3-Clause Yes Details →
1.7.3 15 Mar 2024 M1 BSD-3-Clause Yes Details →
1.7.2 30 Jan 2024 M1 BSD-3-Clause Yes Details →
1.7.1 24 Jan 2024 M1 BSD-3-Clause Yes Details →
1.7.0 27 Dec 2023 M1 BSD-3-Clause Yes Details →
1.6.9 26 Nov 2023 M1 BSD-3-Clause Yes Details →
1.6.8 01 Nov 2023 M1 BSD-3-Clause Yes Details →
1.6.7 10 Oct 2023 M1 BSD-3-Clause Yes Details →
1.6.6 12 Sep 2023 M1 BSD-3-Clause Yes Details →
1.6.5 09 Sep 2023 M1 BSD-3-Clause Yes Details →
1.6.5.rc1 08 Sep 2023 M1 BSD-3-Clause Yes Details →
1.6.4 26 Aug 2023 M1 BSD-3-Clause Yes Details →
1.6.3 16 May 2023 M1 BSD-3-Clause Yes Details →
1.6.2 27 Mar 2023 M1 BSD-3-Clause Yes Details →
1.6.1 22 Feb 2023 M1 BSD-3-Clause Yes Details →
1.6.0 13 Jan 2023 M1 BSD-3-Clause Yes Details →
1.6.0.rc2 04 Jan 2023 M1 BSD-3-Clause Yes Details →
1.6.0.rc1 02 Jan 2023 M1 BSD-3-Clause Yes Details →
1.5.4 18 Nov 2022 M1 BSD-3-Clause Yes Details →
1.5.3 11 Oct 2022 M1 BSD-3-Clause Yes Details →
1.5.2 01 Oct 2022 M1 BSD-3-Clause Yes Details →
1.5.1 30 Sep 2022 M1 BSD-3-Clause Yes Details →
1.5.0 08 Sep 2022 M1 L1 BSD-3-Clause Yes Details →
1.5.0.rc2 30 Aug 2022 M1 BSD-3-Clause Yes Details →
1.5.0.rc1 05 Jul 2022 M1 BSD-3-Clause Yes Details →
1.4.4 14 Jun 2022 M1 BSD-3-Clause Yes Details →
1.4.3 13 Jun 2022 M1 BSD-3-Clause Yes Details →
1.4.2 18 Dec 2019 M1 BSD-3-Clause Yes Details →
1.4.1 29 Apr 2019 M1 BSD-3-Clause Yes Details →
1.4.0 04 Feb 2019 M1 BSD-3-Clause Yes Details →
1.3.13 04 Jan 2017 none BSD-3-Clause — Details →
1.3.12 09 Oct 2016 none BSD-3-Clause — Details →
1.3.11 10 Oct 2015 none BSD-3-Clause — Details →
1.3.10 31 Oct 2014 none BSD-3-Clause — Details →
1.3.9 25 Feb 2014 none BSD-3-Clause — Details →
1.3.8 17 Aug 2013 none MIT — Details →
1.3.7 12 Jan 2013 none — — Details →
1.3.6 16 Apr 2012 none — — Details →
1.3.5 03 Dec 2011 none — — Details →
1.3.4 25 Jul 2011 none — — Details →
1.3.3 16 Jan 2011 none — — Details →
1.3.3.beta.1 14 Jan 2011 none — — Details →
0.1.1 08 May 2010 none — — Details →
0.1.0 02 May 2010 none — — Details →
0.0.8 09 Feb 2010 none — — Details →
0.0.7 04 Feb 2010 none — — Details →
0.0.6 26 Dec 2009 none — — Details →
0.0.5 20 Dec 2009 none — — Details →
0.0.4 09 Dec 2009 none — — Details →
0.0.3 19 Nov 2009 none — — Details →
0.0.2 17 Nov 2009 none — — Details →
0.0.1 17 Nov 2009 none — — Details →
0.0.0 08 Nov 2009 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for sqlite3

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Use-After-Free Vulnerability in sqlite3 Ruby Gem: Aggregate Function Handling 6.3 medium 2.9.6 02 Oct 2026
Vulnerability in SQLite3 Gem's Packaged libsqlite N/A low 1.5.1 03 Oct 2022

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 sqlite3

Is sqlite3 safe to use?

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

Vulert scores sqlite3 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 sqlite3 affected?

No. 2.10.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.

How many vulnerabilities does sqlite3 have?

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

1 vulnerability was recorded for sqlite3 in the last 12 months, and the oldest entry in this database dates to 03 Oct 2022. 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 sqlite3 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 sqlite3 for upcoming vulnerabilities?

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