Summary
Incorrect Lifetime Bounds on Closures in rusqlite
The lifetime bound on several closure-accepting rusqlite functions (specifically, functions which register a callback to be later invoked by SQLite) was too relaxed. If a closure referencing borrowed values on the stack is was passed to one of these functions, it could allow Rust code to access objects on the stack after they have been dropped.
The impacted functions are:
- Under
cfg(feature = "functions"):Connection::create_scalar_function,Connection::create_aggregate_functionandConnection::create_window_function. - Under
cfg(feature = "hooks"):Connection::commit_hook,Connection::rollback_hookandConnection::update_hook. - Under
cfg(feature = "collation"):Connection::create_collation.
The issue exists in all 0.25.* versions prior to 0.25.4, and all 0.26.* versions prior to 0.26.2 (specifically: 0.25.0, 0.25.1, 0.25.2, 0.25.3, 0.26.0, and 0.26.1).
The fix is available in versions 0.26.2 and newer, and also has been back-ported to 0.25.4. As it does not exist in 0.24.*, all affected versions should have an upgrade path to a semver-compatible release.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
rusqlite to 0.26.2 or later; rusqlite to 0.25.4 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-Q89G-4VHH-MVVM? GHSA-Q89G-4VHH-MVVM is a high-severity security vulnerability in rusqlite (rust), affecting versions >= 0.26.0, < 0.26.2. It is fixed in 0.26.2, 0.25.4.
- Which versions of rusqlite are affected by GHSA-Q89G-4VHH-MVVM? rusqlite (rust) versions >= 0.26.0, < 0.26.2 is affected.
- Is there a fix for GHSA-Q89G-4VHH-MVVM? Yes. GHSA-Q89G-4VHH-MVVM is fixed in 0.26.2, 0.25.4. Upgrade to this version or later.
- Is GHSA-Q89G-4VHH-MVVM exploitable, and should I be worried? Whether GHSA-Q89G-4VHH-MVVM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-Q89G-4VHH-MVVM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-Q89G-4VHH-MVVM?
- Upgrade
rusqliteto 0.26.2 or later - Upgrade
rusqliteto 0.25.4 or later
- Upgrade