CVE-2024-44073 is a high-severity (CVSS 7.5) Out-of-bounds Write vulnerability in miniscript. A fix is available for miniscript — see the affected versions and patch details below.
Miniscript allows stack consumption
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-44073.
EPSS Exploitation Probability
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
miniscript🦀miniscript🦀miniscript🦀miniscriptReal-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 Miniscript (aka rust-miniscript) library before 12.2.0 for Rust allows stack consumption because it does not properly track tree depth.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | miniscript | ≥ 12.0.0&&< 12.2.0 | 12.2.0cargo update -p miniscript --precise 12.2.0 |
| 🦀crates.io | miniscript | ≥ 11.0.0&&< 11.2.0 | 11.2.0cargo update -p miniscript --precise 11.2.0 |
| 🦀crates.io | miniscript | ≥ 10.0.0&&< 10.2.0 | 10.2.0cargo update -p miniscript --precise 10.2.0 |
| 🦀crates.io | miniscript | all versions | 9.2.0cargo update -p miniscript --precise 9.2.0 |
Affected Products
miniscriptrust-bitcoinDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for miniscript, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update miniscript to 12.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-44073 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
Is CVE-2024-44073 in your dependencies?
Find it across crates.io, including transitive dependencies.