Skip to main content
VulnerabilityPublished

CVE-2024-46488: sqlite-vec · Heap-based Buffer Overflow

Affects sqlite-vecSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
crates.iosqlite-vecpkg:cargo/sqlite-vecOther threatsAffected
  • =0.1.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate mitigation involves restricting or sanitizing input files processed by applications using sqlite-vec to prevent malformed or malicious files from triggering the vulnerability.
  2. Employ sandboxing or containerization to isolate processes that handle untrusted data, limiting the impact of potential crashes or memory corruption.
  3. Monitor application logs and system behavior for signs of abnormal crashes or memory errors indicative of exploitation attempts.
  4. Implement runtime protections such as Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), and heap protection mechanisms to reduce exploitation success.
  5. Stay alert for official patches or updates from the sqlite-vec maintainers and apply them promptly once available.
  6. Conduct code audits and fuzz testing on the npy_token_next function and related parsing routines to identify and remediate similar vulnerabilities proactively.
  7. If feasible, consider temporarily disabling or replacing the vulnerable component until a fix is released, especially in high-risk environments.
  8. Educate developers and security teams about the risks of processing untrusted input without proper validation and encourage secure coding practices.

Description

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.

References

Community reviews

Loading reviews…