How severe is GHSA-q89g-4vhh-mvvm?

No CVSS score has been assigned to GHSA-q89g-4vhh-mvvm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q89g-4vhh-mvvm?

GHSA-q89g-4vhh-mvvm affects the following packages: rusqlite (crates.io), rusqlite (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-q89g-4vhh-mvvm?

Update rusqlite to 0.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q89g-4vhh-mvvm is resolved across your whole dependency graph.

How do I detect GHSA-q89g-4vhh-mvvm in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rusqlite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q89g-4vhh-mvvm if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-q89g-4vhh-mvvm actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-q89g-4vhh-mvvm, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-q89g-4vhh-mvvm?

GHSA-q89g-4vhh-mvvm has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q89g-4vhh-mvvm?

GHSA-q89g-4vhh-mvvm is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q89g-4vhh-mvvm published, and has it been updated?

GHSA-q89g-4vhh-mvvm was published on June 17, 2022 and was last updated on March 15, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

Incorrect Lifetime Bounds on Closures in `rusqlite`GHSA-q89g-4vhh-mvvm

GHSA-q89g-4vhh-mvvm is a Use After Free vulnerability in rusqlite. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for rusqlite — see the affected versions and patch details below.

Also known asCVE-2021-45713 CVE-2021-45714 CVE-2021-45715 CVE-2021-45716 CVE-2021-45717 CVE-2021-45718

Published

Jun 17, 2022

Updated

Mar 15, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🦀rusqlite🦀rusqlite

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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_function and Connection::create_window_function.
Under cfg(feature = "hooks"): Connection::commit_hook, Connection::rollback_hook and Connection::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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`rusqlite`	≥ 0.26.0&&< 0.26.2	0.26.2`cargo update -p rusqlite --precise 0.26.2`
🦀crates.io	`rusqlite`	≥ 0.25.0&&< 0.25.4	0.25.4`cargo update -p rusqlite --precise 0.25.4`

Affected Products

1 product · 2 configurations

Application

rusqliterusqlite_project

≥ 0.26.0 && < 0.26.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in the rusqlite crate 0.25.x before 0.25.4 and 0…

rustsec.orgNVDJan 2022

Report on raw.githubusercontent.com

raw.githubusercontent.comNVDJan 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rusqlite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rusqlite to 0.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q89g-4vhh-mvvm is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

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_function` and `Connection::create_window_function`. - Under `cfg(feature = "hooks")`: `Connection::commit_hook`, `C

O3 Security · Impact-Aware SCA

Is GHSA-q89g-4vhh-mvvm in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works