Description
mem0 contains unauthenticated config API endpoints that expose LLM API keys in plaintext and allow server-side request forgery via attacker-controlled ollama_base_url parameter. Unauthenticated attackers can retrieve stored secrets like OpenAI API keys via GET /api/v1/config/ or trigger SSRF attacks by setting ollama_base_url to internal addresses like cloud IMDS via PUT /api/v1/config/mem0/llm endpoint.
Published: 2026-07-07
Score: 9.2 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

mem0 contains configuration API endpoints that are accessible without authentication. An attacker can retrieve stored secrets such as OpenAI API keys in plaintext by performing a GET request to /api/v1/config/. In addition, the API allows an unauthenticated PUT to /api/v1/config/mem0/llm where the ollama_base_url parameter can be set to any URL. By providing an attacker‑controlled URL that points to internal services—such as the cloud instance metadata service—an attacker can trigger a server‑side request forgery (SSRF) that enables further compromise of internal resources or data. The combination of plaintext credential disclosure and SSRF makes this a high‑risk vulnerability that can lead to additional privilege escalation or data theft.

Affected Systems

The affected product is mem0, released by the vendor mem0. No specific version information is available in the advisory and therefore all releases of mem0 remain potentially impacted.

Risk and Exploitability

The CVSS score of 9.2 places the vulnerability in the critical range. The EPSS score of < 1% indicates a low but non‑zero probability of exploitation. The issue is not listed in the CISA KEV catalog, meaning there are no known publicly disclosed exploits at this time. However, because the endpoints are unauthenticated and the attacker can influence outbound requests, the risk of exploitation remains high in environments where mem0’s configuration endpoints are reachable from an attacker’s network.

Generated by OpenCVE AI on July 26, 2026 at 18:56 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Adopt the latest mem0 release that removes unauthenticated config endpoints or apply the vendor’s patch commits to disallow unauthenticated GET and PUT requests to /api/v1/config and /api/v1/config/mem0/llm.
  • Restrict outbound network access from mem0 or place the configuration endpoints behind a firewall or reverse‑proxy that requires authentication, preventing unauthenticated callers from reading stored secrets or influencing outbound traffic.
  • Validate and sanitize the ollama_base_url parameter to allow only whitelisted URLs or disable the ability to set it to arbitrary locations, mitigating the SSRF weakness associated with CWE-306.

Generated by OpenCVE AI on July 26, 2026 at 18:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 09 Jul 2026 19:15:00 +0000

Type Values Removed Values Added
Title mem0 - Server-Side Request Forgery and Plaintext API Key Exposure via Unauthenticated Config Endpoints mem0 - Unauthenticated Config API Exposure and SSRF via ollama_base_url

Wed, 08 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 07 Jul 2026 22:45:00 +0000

Type Values Removed Values Added
First Time appeared Mem0
Mem0 mem0
Vendors & Products Mem0
Mem0 mem0

Tue, 07 Jul 2026 21:45:00 +0000

Type Values Removed Values Added
Description mem0 contains unauthenticated config API endpoints that expose LLM API keys in plaintext and allow server-side request forgery via attacker-controlled ollama_base_url parameter. Unauthenticated attackers can retrieve stored secrets like OpenAI API keys via GET /api/v1/config/ or trigger SSRF attacks by setting ollama_base_url to internal addresses like cloud IMDS via PUT /api/v1/config/mem0/llm endpoint.
Title mem0 - Server-Side Request Forgery and Plaintext API Key Exposure via Unauthenticated Config Endpoints
Weaknesses CWE-306
References
Metrics cvssV3_1

{'score': 9.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N'}

cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-07-20T17:45:59.970Z

Reserved: 2026-07-06T15:31:46.187Z

Link: CVE-2026-59706

cve-icon Vulnrichment

Updated: 2026-07-08T13:33:40.376Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-26T19:00:02Z

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function