CVE-2026-115324 mem0ai CVE debrief

Who should care

Defenders responsible for Databricks SQL warehouse configurations and mem0ai deployments should assess their exposure to this vulnerability and prioritize upgrading to version 1.0.8 or later.

Why it matters

Defenders should care about CVE-2026-115324 because it involves an SQL injection vulnerability in mem0ai's Databricks vector store, potentially allowing unauthorized access and data manipulation. Relevant roles include those responsible for Databricks SQL warehouse configurations and mem0ai deployments. Supported consequences include potential unauthorized access and data manipulation. Action priority follows from verifying exposure and upgrading to the fixed version. Evidence limits exist regarding actual exploitation and impact.

• Potential unauthorized access to Databricks SQL warehouse
• Possible data manipulation through injected SQL
• Need for verification of exposure in current configurations
• Priority on upgrading to fixed version 1.0.8 or later

Technical summary

The mem0ai library versions 0.1.117 through 1.0.7 contain an SQL injection vulnerability in the mem0/vector_stores/databricks.py file. This vulnerability allows attackers to inject SQL by influencing stored memory content, metadata, or message names that reach unescaped insert() and update() string interpolation, potentially leading to unauthorized access and data manipulation in the configured Databricks SQL warehouse.

Defensive priority

Defenders should prioritize verifying exposure in their Databricks SQL warehouse configurations and upgrading to mem0ai version 1.0.8 or later.

Recommended defensive actions

• Verify exposure in Databricks SQL warehouse configurations
• Upgrade to mem0ai version 1.0.8 or later
• Review stored memory content, metadata, and message names for potential SQL injection attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability exists in mem0ai versions 0.1.117 through 1.0.7 due to an SQL injection issue in the mem0/vector_stores/databricks.py file. Attackers can inject SQL by influencing stored memory content, metadata, or message names that reach unescaped insert() and update() string interpolation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.