Vulnerability Database · Debian · Package report

sqlite3: vulnerability history, versions and safety

sqlite3 is a package in the Debian ecosystem. Vulert records 5 vulnerabilities for it across 6 releases, from May 2015 to May 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded U5
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.

Vulert verdict on sqlite3 i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 26 May 2020. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 5 vulnerabilities on record across 5 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 5 years · 0 in the last year i
  • Latest disclosure 26 May 2020 i
  • Highest CVSS n/a i
  • With no published fix 0 i

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 holds for sqlite3, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
3.8.7.1-1 U5 Yes Details →
3.8.7.1-1+deb8u5 U1 Yes Details →
3.8.7.1-1+deb8u4 U2 Yes Details →
3.8.7.1-1+deb8u3 U3 Yes Details →
3.8.7.1-1+deb8u2 U4 Yes Details →
3.8.7.1-1+deb8u1 U4 Yes Details →

Newest 6 of 6 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2015 1
  • 2018 1
  • 2019 1
  • 2020 2

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

03 Vulnerabilities

Recorded vulnerabilities for sqlite3

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical SQLite3 Vulnerability in Debian 8 Jessie N/A unrated 3.8.7.1-1+deb8u3 22 Dec 2018
SQLite3 - Multiple Vulnerabilities N/A unrated 3.8.7.1-1+deb8u4 11 Jan 2019
SQLite3 - Denial of Service Vulnerability N/A unrated 3.8.7.1-1+deb8u5 05 May 2020
Integer Overflow Vulnerability in sqlite3 N/A unrated 3.8.7.1-1+deb8u6 26 May 2020
Security Update for sqlite3 Package N/A unrated 3.8.7.1-1+deb8u1 06 May 2015

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 5 vulnerabilities for sqlite3 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does sqlite3 have?

5 vulnerabilities are recorded for sqlite3 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. 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?

0 vulnerabilities were recorded for sqlite3 in the last 12 months, and the oldest entry in this database dates to 06 May 2015. 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.