sqlite3 Security Analysis
sqlite3 has 2 known security vulnerabilities in RubyGems (Ruby). Upgrade to version 2.9.5 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 2.9.5
Upgrading to 2.9.5 or later resolves all 2 known vulnerabilities in sqlite3. Run: gem install sqlite3 -v 2.9.5
Is sqlite3 in your project?
Check if you're affected and upgrade to 2.9.5 to stay secure.
Vulnerabilities
2 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details.
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-54620 sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks | LOW | 2.1.0, 2.1.1, 2.2.0, 2.3.0 (+19 more) | 2.9.5 |
| CVE-2026-54619 sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity | LOW | 0.0.0, 0.0.1, 0.0.2, 0.0.3 (+79 more) | 2.9.5 |
About This Data
Vulnerability data for sqlite3 is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related RubyGems (Ruby) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of sqlite3.