Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-54619

sqlite3-ruby: sqlite3: sqlite3-ruby: Use-after-free when redefining SQLite functions with different arity

Overview

Published
28 Jul 2026
Modified
23 Oct 2026
Low CVE
2 Registry packages
2 OS packages
3 Linux distributions
Yes Fix available

Description

sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version 2.9.5.

Source: OX vulnerability database

Severity

4.5 · LOW

CVSS 3.1 base score, scored by redhat.

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

Weakness: CWE-416

Affected packages · 2

Packages affected by CVE-2026-54619
EcosystemPackageVulnerableFixed in
RubyGems sqlite3 <2.9.5 2.9.5
RubyGems sqlite3-ruby <2.9.5 2.9.5

Open a package to see all its vulnerabilities.

Operating systems · 7 fixes

Red Hat 2 releases · 1 package

affected 2
rubygem-sqlite3
Red Hat fixes for CVE-2026-54619
ReleasePackageFixed in
7 rubygem-sqlite3 affected
7 (satellite:el8) rubygem-sqlite3 affected

debian 4 releases · 1 package

affected 3 fixed 1
ruby-sqlite3
debian fixes for CVE-2026-54619
ReleasePackageFixed in
11 ruby-sqlite3 affected
12 ruby-sqlite3 affected
13 ruby-sqlite3 affected
14 ruby-sqlite3 2.9.5-1

echo 1 release · 1 package

affected 1
ruby-sqlite3
echo fixes for CVE-2026-54619
ReleasePackageFixed in
ruby-sqlite3 affected

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.