How severe is CVE-2021-45714?

CVE-2021-45714 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-45714?

CVE-2021-45714 affects the following packages: rusqlite (crates.io), rusqlite (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2021-45714?

Update rusqlite to 0.25.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-45714 is resolved across your whole dependency graph.

How do I detect CVE-2021-45714 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 CVE-2021-45714 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 CVE-2021-45714 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2021-45714, 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 CVE-2021-45714?

CVE-2021-45714 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 CVE-2021-45714?

CVE-2021-45714 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 CVE-2021-45714 published, and has it been updated?

CVE-2021-45714 was published on December 26, 2021 and was last updated on October 24, 2026. 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

HIGH severity

CVE-2021-45714 — rusqlite

HIGH

CVE-2021-45714 is a high-severity (CVSS 7.5) 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.

Use After Free in rusqlite

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

Published

Dec 26, 2021

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

Exploitation data as of Nov 3, 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.

How urgent is this, really

Where this sits among everything scored

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

An issue was discovered in the rusqlite crate 0.25.x before 0.25.4 and 0.26.x before 0.26.2 for Rust. create_aggregate_function has a use-after-free.

Affected Packages

2 total 2 fixed

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

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.25.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-45714 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

An issue was discovered in the rusqlite crate 0.25.x before 0.25.4 and 0.26.x before 0.26.2 for Rust. create_aggregate_function has a use-after-free.

O3 Security · Impact-Aware SCA

Is CVE-2021-45714 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-416Use After Free

Weaponization

No Nuclei template or Metasploit module yet. 2 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

rusqlite

5.2/10

Maintained10/10

Code-Review4/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Dec 26, 2021

First exploit

Jan 6, 2022

Last updated

Oct 24, 2026

Identifiers

CVE-2021-45714

GHSA-4qr3-m7ww-hh9g

RUSTSEC-2021-0128

References

Advisorynvd.nist.gov · CVE 2021 45717 Reportrustsec.org · RUSTSEC 2021 0128 Webgithub.com Packagegithub.com · rusqlite Evidenceraw.githubusercontent.com · RUSTSEC 2021 0128.md

Related vulnerabilities

This CVE is high severity; 8 of 8 other CVEs affecting rusqlite are rated as high or higher (top: critical).

GHSA-q89g-4vhh-mvvmCVE-2021-45717CVE-2021-45715CVE-2021-45713CVE-2021-45716CVE-2021-45718CVE-2021-45719CVE-2020-35867

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2021-45714 — rusqlite

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-45714 in your dependencies?