Summary
sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity
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.
Impact
Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
sqlite3-ruby to 2.9.5 or later; sqlite3 to 2.9.5 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-54619? CVE-2026-54619 is a low-severity use after free vulnerability in sqlite3-ruby (rubygems), affecting versions <= 2.9.4. It is fixed in 2.9.5. Memory is accessed after it has been freed, leading to undefined behavior in native code.
- Which packages are affected by CVE-2026-54619?
sqlite3-ruby(rubygems) (versions <= 2.9.4)sqlite3(rubygems) (versions <= 2.9.4)
- Is there a fix for CVE-2026-54619? Yes. CVE-2026-54619 is fixed in 2.9.5. Upgrade to this version or later.
- Is CVE-2026-54619 exploitable, and should I be worried? Whether CVE-2026-54619 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-54619 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-54619?
- Upgrade
sqlite3-rubyto 2.9.5 or later - Upgrade
sqlite3to 2.9.5 or later
- Upgrade