AIKIDO-2026-11126

TL;DR

The sqlite3 Ruby gem wires aggregate function callbacks from Ruby into SQLite through the native extension. If a prepared statement that calls a user-defined aggregate is stepped after the database is soft-closed, SQLite may invoke callback objects that were released when the database cleared its aggregator references, and garbage collection can cause an invalid memory read and segmentation fault. Applications that keep statements open across close while using create_aggregate, create_aggregate_handler, or define_aggregator can crash. Version 2.9.5 stops clearing aggregator references on close so callbacks remain valid for open statements.