CVE-2026-54619: sparklemotion sqlite3-ruby use-after-free in function redefinition

CVE-2026-54619 · Severity: medium · CVSS 4 · Published 2026-07-28

The sqlite3-ruby library, which allows Ruby applications to interact with SQLite databases, contains a memory management flaw. When a developer redefines a custom database function with a different number of arguments, the library may incorrectly free memory that is still in use. This can lead to application crashes (segmentation faults) or unpredictable behavior, potentially impacting the reliability of services using this library.

Technologies: sqlite3 (RubyGems), sqlite3-ruby (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2026-54619 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-54619 being exploited in the wild.
How severe is CVE-2026-54619?
Medium severity, with a CVSS score of 4, published 28 July 2026.
Which products and versions are affected?
sqlite3 (RubyGems) <= 2.9.4, ECOSYSTEM:introduced=0,fixed=2.9.5; sqlite3-ruby (RubyGems) <= 2.9.4, ECOSYSTEM:introduced=0,fixed=2.9.5.
Is there a fix for CVE-2026-54619?
Yes. sqlite3 (RubyGems): upgrade to 2.9.5 or later; sqlite3-ruby (RubyGems): upgrade to 2.9.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54619 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-54619?
Check whether you run sqlite3 (RubyGems) or sqlite3-ruby (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • sqlite3 (RubyGems): upgrade to 2.9.5 or later
    bundle update sqlite3
  • sqlite3-ruby (RubyGems): upgrade to 2.9.5 or later
    bundle update sqlite3-ruby

Technical details

A use-after-free vulnerability exists in the Ruby bindings for SQLite3 (sqlite3-ruby) within the `Database#create_function` and `Database#define_function` methods. When a function is redefined with a different arity (number of arguments) or text encoding, the library frees the previously registered function handler while the underlying SQLite engine may still maintain a reference to it. This occurs because the handler's lifecycle is not correctly synchronized with SQLite's internal state. An attacker or a specific code execution flow can trigger this after garbage collection, resulting in a segmentation fault or memory corruption. The issue is fixed in version 2.9.5.

Affected products

  • sparklemotion sqlite3-ruby <= 2.9.4

Identifiers

  • CVE-2026-54619
  • GHSA-28hh-pr2h-2w89

Timeline

  • 2026-06-07: patched: Version 2.9.5 released
  • 2026-06-07: advisory: GitHub Security Advisory GHSA-28hh-pr2h-2w89 published
  • 2026-07-28: disclosed: CVE-2026-54619 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.