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.
CVE-2026-115324
HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-22. A secondary CVSS source baseline 8.1; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-108126 (ENISA EUVD) · GHSA-7587-9684-52r6 (GitHub Security Advisories)Source: ENISA EUVD
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 8.1HIGHhigh confidence
- EG Risk
- 37EG Risk 37/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity81% × 45%Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 25th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 22, 2026
Last Modified
October 29, 2026
Advisory Details (7)
Auto-updated Oct 22, 2026Patch available. Sources: github_pr, github_commit, github_release.
Web page
mem0 0.1.117 before 1.0.8 SQL Injection via Databricks Vector Store | Advisories | VulnCheck
https://www.vulncheck.com/advisories/mem0-0.1.117-before-1.0.8-sql-injection-via-databricks-vector-storeWeb page
GitHub - mem0ai/mem0: The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production. · GitHub
https://github.com/mem0ai/mem0Web page
mem0/mem0/vector_stores/databricks.py at v1.0.7 · mem0ai/mem0 · GitHub
https://github.com/mem0ai/mem0/blob/v1.0.7/mem0/vector_stores/databricks.pyGitHub release Patch Available
v1.0.8
Patch available: mem0ai/mem0 v1.0.8
https://github.com/mem0ai/mem0/releases/tag/v1.0.8GitHub commit Patch Available
commit a2ffca326605 (mem0ai/mem0)
Patch available: mem0ai/mem0 v2.0.19 (contains commit a2ffca326605)
https://github.com/mem0ai/mem0/commit/a2ffca32660537b7b304305f36774ae2a13452cbGitHub pull request Patch Available
fix: prevent SQL injection in Databricks vector store
Patch available: mem0ai/mem0 v2.0.19 (PR #4558 merged 2026-03-26)
https://github.com/mem0ai/mem0/pull/4558Web page
Security: SQL injection in Databricks vector store via f-string interpolation · Issue #4073 · mem0ai/mem0 · GitHub
https://github.com/mem0ai/mem0/issues/4073Vendor Advisories for CVE-2026-115324(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| mem0ai | 0.1.117 ... 1.0.7 (11 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 16× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-29 12:27 UTCEG score recompute
- 2026-10-29 11:33 UTCEG score recompute
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-27 20:43 UTCEG score recompute
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-25 14:50 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-22 17:47 UTCEG score recompute
- 2026-10-22 17:47 UTCGHSA enrichmentGHSA-7587-9684-52r6 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-22 11:26 UTCEG score recompute
- 2026-10-22 11:01 UTCEG score recomputeFirst assessed: 8.1 HIGH
- 2026-10-22 11:00 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
5 shownPyPI:mem0ai
Frequently asked(5)
What is CVE-2026-115324?
CVE-2026-115324 is a high-severity vulnerability; its CVE record was published on October 22, 2026. 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…
When was CVE-2026-115324 made public?
CVE-2026-115324 was made public on March 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 22, 2026. EchelonGraph's copy of the record carries a last-modified date of October 29, 2026; the record at its source may have been updated since.
Is CVE-2026-115324 actively exploited?
CVE-2026-115324 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-115324?
CVE-2026-115324 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-115324?
A fix for CVE-2026-115324 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-115324 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-115324
Is Your Infrastructure Affected by CVE-2026-115324?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.