GHSA-28hh-pr2h-2w89: sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity

lowCVE-2026-54619

Summary Using Database#create_function or Database#define_function to define the same function name more than once with different numbers of arguments ("arity") or text encodings will result in a invalid memory read and a segmentation fault. Mitigation Upgrade to sqlite3 gem v2.9.5 or later. As a workaround, avoid defining multiple custom functions with the same name (varying numbers of arguments or encoding). Severity The sqlite3-ruby maintainers assess this as Low severity. It is reliably triggered after GC when code is structured in a particular way. There is no known general exploit that could be used as a denial of service attack.

Details

Source: GitHub Security Advisories (INTL · database · site)
Severity: low
Published: 2026-07-28
Last updated: 2026-07-28
Exploitation: Not in CISA KEV at last sync

Original advisory: https://github.com/advisories/GHSA-28hh-pr2h-2w89

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2026-546190.11% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 1% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-54619	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

unknownCVE-2026-54619: sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier…nvd

GHSA-28hh-pr2h-2w89: sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity

Details

Exploitation outlook

Referenced CVEs

Same CVEs, other sources

More from GitHub Security Advisories