CVE-2024-46488 — sqlite-vec
CRITICALCVE-2024-46488 is a critical-severity (CVSS 9.1) Out-of-bounds Write vulnerability in sqlite-vec. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for sqlite-vec — see the affected versions and patch details below.
Heap-based Buffer Overflow in sqlite-vec
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-46488.
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
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
sqlite-veccrates.ioDescription
sqlite-vec v0.1.1 was discovered to contain a heap buffer overflow via the npy_token_next function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted file.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | sqlite-vec | all versions | 0.1.3cargo update -p sqlite-vec --precise 0.1.3 |
| 📦npm | sqlite-vec | all versions | 0.1.3npm install sqlite-vec@0.1.3 |
| 🐍PyPI | sqlite-vec | all versions | 0.1.3pip install --upgrade 'sqlite-vec==0.1.3' |
| 💎RubyGems | sqlite-vec | all versions | 0.1.3bundle update sqlite-vec --conservative |
Affected Products
sqlite-vecasg017Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sqlite-vec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sqlite-vec to 0.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-46488 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-46488 in your dependencies?
Find it across crates.io, npm, PyPI, including transitive dependencies.