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

Affected: Homebrew: mailcatcher

## 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.

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

Affected: sparklemotion sqlite3-ruby

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.

Most recent entries from all

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

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