Is sqlite3-ruby 1.1 vulnerable?
RubyGems · 1 release from 1.1.0 to 1.1.0 · latest sqlite3-ruby is 1.3.3 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. sqlite3-ruby 1.1.0, the last 1.1 release, is affected by 2 known security advisories (2 low), including CVE-2026-54619, CVE-2011-0995. 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.1.0
sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity
- Affected
- <2.9.5
- Fixed in
- 2.9.5
sqlite3-ruby uses weak permissions for unspecified files, which allows local users to gain privileges
- Affected
- <1.2.4
- Fixed in
- 1.2.4
Which of your client projects are still on sqlite3-ruby 1.1?
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.