CVE-2026-115324

waiting for further signalsZero needs more public information before it can validate it.

GHSA-7587-9684-52r6 ↗EUVD-2026-108126 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
mem0ai mem0 >= 0.1.117, < 1.0.8
fixed in 1.0.8
ETK-2026-2440Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 42msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h15m
0
+4h
+6h
+8h
+10h
+12h

description

mem0 versions 0.1.117 through versions earlier than 1.0.8 are affected in the Databricks vector-store path. An attacker who can control stored memory-related content may cause unintended SQL to run against the configured Databricks SQL warehouse; this requires that the Databricks integration is enabled and attacker-influenced content reaches it.

mitigation

Upgrade mem0 to version 1.0.8 or later. Until upgraded, disable the Databricks vector-store integration or prevent untrusted content from being stored through it.

fixed in 1.0.8

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 10:57Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-22 10:57Z
    ghsa: trigger signal, started the run
  2. 2026-10-22 10:57Z

this entry in the feed

GET /api/v1/feed/CVE-2026-115324

{
  "etk_id": "ETK-2026-2440",
  "cve_id": "CVE-2026-115324",
  "display_id": "CVE-2026-115324",
  "ghsa_id": "GHSA-7587-9684-52r6",
  "euvd_id": "EUVD-2026-108126",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in mem0 Databricks vector store",
  "summary": "mem0 versions 0.1.117 through versions earlier than 1.0.8 are affected in the Databricks vector-store path. An attacker who can control stored memory-related content may cause unintended SQL to run against the configured Databricks SQL warehouse; this requires that the Databricks integration is enabled and attacker-influenced content reaches it.",
  "mitigation": "Upgrade mem0 to version 1.0.8 or later. Until upgraded, disable the Databricks vector-store integration or prevent untrusted content from being stored through it.",
  "vendor": "mem0ai",
  "product": "mem0",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.1.117, < 1.0.8"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.0.8"
      ],
      "package_name": "mem0",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.228601633333334,
  "t0_at": "2026-10-22T10:57:43.136000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T10:57:43.136000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T10:57:43.136000+00:00",
      "url": "https://github.com/advisories/GHSA-7587-9684-52r6"
    }
  }
}

published 2026-10-22 13:01Z
last change 2026-10-22 15:59Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.