NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · RubyGems

CVE-2026-54619: sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity

lowCVSS 4.0 2.0GHSA-28hh-pr2h-2w89

Summary Using Database#createfunction or Database#definefunction 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).

Published Jul 28, 2026

Affected packages

sqlite3-ruby

Ecosystem
RubyGems
Affected
<= 2.9.4
Fixed in
2.9.5
Check
bundle info sqlite3-ruby

sqlite3

Ecosystem
RubyGems
Affected
<= 2.9.4
Fixed in
2.9.5
Check
bundle info sqlite3

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to cla7aye15I4nd.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More RubyGems vulnerabilities

All RubyGems entries