What is CVE-2024-46488?

CVE-2024-46488 is a high-severity out-of-bounds write vulnerability in sqlite-vec (pip), affecting versions < 0.1.3. It is fixed in 0.1.3. A write operation targets a memory location beyond the intended buffer boundary.

How severe is CVE-2024-46488?

CVE-2024-46488 has a CVSS score of 9.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of sqlite-vec are affected by CVE-2024-46488?

sqlite-vec (pip) versions < 0.1.3 is affected.

Is there a fix for CVE-2024-46488?

Yes. CVE-2024-46488 is fixed in 0.1.3. Upgrade to this version or later.

Is CVE-2024-46488 exploitable, and should I be worried?

Whether CVE-2024-46488 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-46488 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-46488 in sqlite-vec

Q: How severe is CVE-2024-46488?

CVE-2024-46488 has a CVSS score of 9.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of sqlite-vec are affected by CVE-2024-46488?

sqlite-vec (pip) versions < 0.1.3 is affected.

Q: Is there a fix for CVE-2024-46488?

Yes. CVE-2024-46488 is fixed in 0.1.3. Upgrade to this version or later.

Q: Is CVE-2024-46488 exploitable, and should I be worried?

Whether CVE-2024-46488 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-46488 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-46488?

Upgrade: sqlite-vec to 0.1.3 or later, sqlite-vec to 0.1.3 or later, sqlite-vec to 0.1.3 or later, sqlite-vec to 0.1.3 or later.

Summary

Heap-based Buffer Overflow in sqlite-vec

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.

Impact

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

CVE-2024-46488 has a CVSS score of 9.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.1.3); upgrading removes the vulnerable code path.

Affected versions

sqlite-vec (< 0.1.3) sqlite-vec (< 0.1.3) sqlite-vec (< 0.1.3) sqlite-vec (< 0.1.3)

Security releases

sqlite-vec → 0.1.3 (pip) sqlite-vec → 0.1.3 (npm) sqlite-vec → 0.1.3 (rubygems) sqlite-vec → 0.1.3 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

sqlite-vec to 0.1.3 or later; sqlite-vec to 0.1.3 or later; sqlite-vec to 0.1.3 or later; sqlite-vec to 0.1.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-46488? CVE-2024-46488 is a high-severity out-of-bounds write vulnerability in sqlite-vec (pip), affecting versions < 0.1.3. It is fixed in 0.1.3. A write operation targets a memory location beyond the intended buffer boundary.
How severe is CVE-2024-46488? CVE-2024-46488 has a CVSS score of 9.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of sqlite-vec are affected by CVE-2024-46488? sqlite-vec (pip) versions < 0.1.3 is affected.
Is there a fix for CVE-2024-46488? Yes. CVE-2024-46488 is fixed in 0.1.3. Upgrade to this version or later.
Is CVE-2024-46488 exploitable, and should I be worried? Whether CVE-2024-46488 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-46488 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-46488?
- Upgrade sqlite-vec to 0.1.3 or later
- Upgrade sqlite-vec to 0.1.3 or later
- Upgrade sqlite-vec to 0.1.3 or later
- Upgrade sqlite-vec to 0.1.3 or later