Mem0 Unauthenticated API Exposes LLM API Keys and Permits SSRF
mem0
Mem0 contains unauthenticated config API endpoints that expose plaintext LLM API keys and allow server-side request forgery via the ollama_base_url parameter. Attackers can retrieve stored secrets and target internal metadata services.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 9.3
- EPSS
- <0.01 · top 62% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 7 Jul 2026
- last update
- 7 Jul 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-07-07CVE-2026-59706: mem0 contains unauthenticated config API endpoints that expose LLM API keys in plaintext and allow server-side request forgery…NVD · nvd.nist.gov/vuln/detail/CVE-2026-59706
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerabilityData leak
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- mitre atlas
- no technique for these categories
- dates
- happened 7 Jul 2026 · first reported 7 Jul 2026
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 10:04Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# Mem0 Unauthenticated API Exposes LLM API Keys and Permits SSRF https://gcdradar.vercel.app/incidents/mem0-unauthenticated-api-exposes-llm-api-keys-and-permits-ss · AIR-2026-1154 · closed 2026-07-07 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-07-07 - AI role: Attack on AI - Products: mem0 - CVE ids: CVE-2026-59706 - CVSS: 9.3 ## Summary Mem0 contains unauthenticated config API endpoints that expose plaintext LLM API keys and allow server-side request forgery via the ollama_base_url parameter. Attackers can retrieve stored secrets and target internal metadata services. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-07-07: CVE-2026-59706: mem0 contains unauthenticated config API endpoints that expose LLM API keys in plaintext and allow server-side request forgery… (https://nvd.nist.gov/vuln/detail/CVE-2026-59706) ## Sources - 2026-07-07 NVD: CVE-2026-59706: mem0 contains unauthenticated config API endpoints that expose LLM API keys in plaintext and allow server-side request forgery… https://nvd.nist.gov/vuln/detail/CVE-2026-59706 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed7.4Langflow CVE-2026-8470: IBM Langflow OSS Weak Cryptographic Key Generation
Patch now · Disclosed · since 5 Aug 2026 · CVE-2026-8470
AI - closed7.1Langflow IBM Langflow OSS authorization bypass in MemoryComponent leads to chat history exposure
Patch now · Disclosed · since 5 Aug 2026 · CVE-2026-9130
AI - closed9.1Langflow CVE-2026-9205: Langflow Weak Fernet Key Derivation via random.seed()
Patch now · Disclosed · since 5 Oct 2026 · updated 5 Oct 2026 · CVE-2026-9205
AI - closed7.6Flowise CVE-2026-70474: Flowise Cross-Workspace OAuth2 Credential Metadata Leak
Patch now · Disclosed · since 4 Aug 2026 · CVE-2026-70474
AI - closed8.3Flowise CVE-2026-70473: Flowise Information Disclosure via Upsert History
Patch now · Disclosed · since 4 Aug 2026 · CVE-2026-70473
AI - closedFlowise Flowise incomplete credential redaction exposes secrets
Patch now · Disclosed · since 4 Aug 2026
AI