VulertSecurity VulertSecurity

Vulnerability Database · Ubuntu · Package report

sqlite3: vulnerability history, versions and safety

sqlite3 is a package in the Ubuntu ecosystem. Vulert records 20 vulnerabilities for it across 13 releases, from Sep 2016 to Jul 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
20 vulnerabilities recorded U20
i
3 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 sqlite3 vulnerabilities

Vulert verdict on sqlite3 i

Updated on 23 Oct 2026

Careful: 3 of the 20 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 20 vulnerabilities on record across 8 years, none in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 20 over 8 years · 0 in the last year i
  • Latest disclosure 29 Jul 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 3 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2016 1
  • 2017 3
  • 2018 1
  • 2019 9
  • 2022 4
  • 2024 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for sqlite3

The 5 most severe of 20 vulnerabilities recorded for this package

Search all 20 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Out of Bounds Access Vulnerability in SQLite3 Package 9.8 critical No fix published 01 Sep 2022
Critical Buffer Over-read Vulnerability in SQLite3 Package 9.8 critical 3.8.2-1ubuntu2.2+esm1 07 Jul 2017
Critical Buffer Overflow Vulnerability in SQLite3 Package 9.8 critical 3.8.2-1ubuntu2.2+esm1 22 May 2017
Critical Out of Bounds Write Vulnerability in SQLite Package - CVE-2019-13734 8.8 high 3.8.2-1ubuntu2.2+esm2 10 Dec 2019
Critical Buffer Overflow Vulnerability in SQLite3 Package: CVE-2018-20346 8.1 high 3.8.2-1ubuntu2.2+esm1 21 Dec 2018

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 20 vulnerabilities for sqlite3 in Ubuntu: 0 critical, 0 high, 0 medium and 0 low, plus 20 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does sqlite3 have?

20 vulnerabilities are recorded for sqlite3 in the Ubuntu ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 20 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 26 Sep 2016. 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.