Is sqlite3-ruby 1.2 vulnerable?

RubyGems · 6 releases from 1.2.0 to 1.2.5 · latest sqlite3-ruby is 1.3.3 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. sqlite3-ruby 1.2.5, the last 1.2 release, is affected by 1 known security advisory (1 low), including CVE-2026-54619. 1 more affects earlier 1.2.x releases. Upgrade to 2.9.5 or later to fix all of them.

Upgrade with:bundle update --conservative sqlite3-ruby # Gemfile: '>= 2.9.5'

Is your project on an affected sqlite3-ruby?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.2.5

  • LowCVE-2026-54619GHSA-28hh-pr2h-2w8928 Jul 2026

    sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity

    Affected
    <2.9.5
    Fixed in
    2.9.5

Fixed within 1.2.x, affecting earlier releases

  • LowCVE-2011-0995GHSA-6x46-7rrv-m4h824 Oct 2017

    sqlite3-ruby uses weak permissions for unspecified files, which allows local users to gain privileges

    Affected
    <1.2.4
    Fixed in
    1.2.4

Every sqlite3-ruby 1.2.x release

Affected: 1.2.0 to 1.2.5. Latest sqlite3-ruby: 1.3.3.

VersionKnown advisories
sqlite3-ruby 1.2.5CVE-2026-54619
sqlite3-ruby 1.2.4CVE-2026-54619
sqlite3-ruby 1.2.3CVE-2026-54619, CVE-2011-0995
sqlite3-ruby 1.2.2CVE-2026-54619, CVE-2011-0995
sqlite3-ruby 1.2.1CVE-2026-54619, CVE-2011-0995
sqlite3-ruby 1.2.0CVE-2026-54619, CVE-2011-0995

Which of your client projects are still on sqlite3-ruby 1.2?

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.