Skip to content
Fencer Vulns
low 2.0

CVE-2026-54619 json

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

published 2026-07-28 3 mo ago modified 2026-10-23 16 d ago also GHSA-28hh-pr2h-2w89 , EUVD-2026-49896

cvss
2.0
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits
0
none known

Summary

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.

Patch / fix

  • rubygems sqlite3-ruby 2.9.5
  • rubygems sqlite3 2.9.5
  • ruby-sqlite3 Debian 14 2.9.5-1

debian advisories DEBIAN-CVE-2026-54619

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-54619 updated cvss 4.5

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

  • Red Hat Satellite 6 rubygem-sqlite3
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 2.0 CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
CNA 4.0 2.0 CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
rubygems sqlite3-ruby
<2.9.5
2.9.5
rubygems sqlite3
<2.9.5
2.9.5

Affected products

  • sparklemotion sqlite3-ruby

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.