SQLite vulnerabilities: known CVEs & security history
SQLite · Database · 8 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all SQLite release lines — 8 in total. A CVE here doesn't mean your version is affected — check SQLite's current status and the safe version to run.
Known SQLite CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-51297 | high | 8.8 | 0% | 2026 |
| CVE-2026-11824 | high | 7.8 | 0% | 2026 |
| CVE-2026-11822 | high | 7.8 | 0% | 2026 |
| CVE-2025-6965 | high | 7.7 | 73% | 2025 |
| CVE-2026-51304 | high | 7.5 | 0% | 2026 |
| CVE-2026-51302 | high | 7.5 | 1% | 2026 |
| CVE-2026-51296 | high | 7.5 | 0% | 2026 |
| CVE-2026-51298 | medium | 6.2 | 0% | 2026 |
Is my SQLite version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your SQLite version → · Monitor SQLite for new CVEs →
SQLite vulnerabilities — frequently asked
How many known vulnerabilities does SQLite have?
IsItPatched tracks 8 CVEs for SQLite. 0 are critical-severity and 7 high-severity. These span every release line — what matters is whether the version you run is affected.
Does SQLite have any actively-exploited vulnerabilities?
None of SQLite's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe SQLite vulnerability?
Among tracked issues, CVE-2026-51297 (HIGH, CVSS 8.8) ranks highest — a Use-after-free weakness.
Is SQLite safe to use?
It depends on the version. The latest supported SQLite release (3.53.4) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: SQLite security status · SQLite end-of-life · actively-exploited CVEs. Always verify against SQLite's advisories — see our disclaimer.