Live › vulnerability › CVE-2026-115324
Go to dashboardmem0ai's Databricks vector store builds SQL by string interpolation in its insert and update paths, so memory text, metadata, or message names can carry injected SQL. An attacker who can influence stored memory content can run arbitrary SQL against the configured Databricks SQL warehouse.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 20:59 UTC, 1h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| mem0ai | pypi | >= 0.1.117, < 1.0.8 | 1.0.8 |
pip show mem0ai (or pip list | grep mem0ai); vulnerable if version is >= 0.1.117 and < 1.0.8databricks in the Memory config / config file; code uses mem0/vector_stores/databricks.py)1.0.8 or later (pip install -U mem0ai>=1.0.8)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
mem0 0.1.117 before 1.0.8 contains an sql injection vulnerability in mem0/vector_stores/databricks.py that allows attackers to inject SQL by influencing stored memory content. Attackers can supply crafted memory text, metadata, or message names that reach unescaped insert() and update() string interpolation to execute injected SQL on the configured Databricks SQL warehouse.
This page as .md · .json · in your agent: get_signal("CVE-2026-115324")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.