Is sqlite3-ruby 1.3 vulnerable?
RubyGems · 4 releases from 1.3.0 to 1.3.3 · latest sqlite3-ruby is 1.3.3 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. sqlite3-ruby 1.3.3, the last 1.3 release, is affected by 1 known security advisory (1 low), including CVE-2026-54619. Upgrade to 2.9.5 or later to fix all of them.
bundle update --conservative sqlite3-ruby # Gemfile: '>= 2.9.5'Is your project on an affected sqlite3-ruby?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting sqlite3-ruby 1.3.3
sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity
- Affected
- <2.9.5
- Fixed in
- 2.9.5
Every sqlite3-ruby 1.3.x release
Affected: 1.3.0 to 1.3.3.
| Version | Known advisories |
|---|---|
| sqlite3-ruby 1.3.3 | CVE-2026-54619 |
| sqlite3-ruby 1.3.2 | CVE-2026-54619 |
| sqlite3-ruby 1.3.1 | CVE-2026-54619 |
| sqlite3-ruby 1.3.0 | CVE-2026-54619 |
Which of your client projects are still on sqlite3-ruby 1.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact sqlite3-ruby version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other sqlite3-ruby versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.