CVE-2026-54619 sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity
Redefining SQLite functions with different arity in sqlite3-ruby causes a use-after-free, potentially allowing code execution or crashes.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54619?
CVE-2026-54619 is a low-severity use after free vulnerability in sparklemotion sqlite3-ruby, published on 28 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-416
Which versions are affected by CVE-2026-54619?
4 open source packages ship an affected version, including sqlite3-ruby and sqlite3.
| Package | Affected | Fixed in |
|---|---|---|
sqlite3-ruby RubyGems | All versions | 2.9.5 |
sqlite3-ruby RubyGems | All versions | 2.9.5 |
sqlite3 RubyGems | All versions | 2.9.5 |
sqlite3 RubyGems | All versions | 2.9.5 |
How do I fix CVE-2026-54619?
Upgrade sqlite3-ruby to 2.9.5 or later.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2026-54619 being exploited?
There is no known exploitation of CVE-2026-54619 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2026-54619, GHSA-28hh-pr2h-2w89, UBUNTU-CVE-2026-54619.