CVE-2026-59706
Deferred Deferred - Pending Action

mem0 Unauthenticated Config API Exposes LLM Keys and SSRF

Vulnerability report for CVE-2026-59706, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-07

Last updated on: 2026-07-08

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-07
Last Modified
2026-07-08
Generated
2026-07-15
AI Q&A
2026-07-08
EPSS Evaluated
2026-07-14
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
mem0ai mem0 to a3154d5 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in mem0, which has unauthenticated configuration API endpoints. These endpoints expose large language model (LLM) API keys in plaintext, allowing attackers to retrieve sensitive secrets such as OpenAI API keys without authentication. Additionally, attackers can exploit the vulnerability to perform server-side request forgery (SSRF) by manipulating the ollama_base_url parameter to make the server send requests to internal addresses.

Compliance Impact

This vulnerability exposes LLM API keys in plaintext through unauthenticated config API endpoints, allowing attackers to retrieve sensitive secrets and perform server-side request forgery. Such exposure of sensitive credentials can lead to unauthorized access and data breaches, which may violate data protection requirements under common standards and regulations like GDPR and HIPAA.

Specifically, the leakage of API keys and potential misuse of internal services could compromise confidentiality and integrity of data, thereby impacting compliance with regulations that mandate strict controls over access to sensitive information.

Impact Analysis

The vulnerability can have severe impacts including unauthorized disclosure of sensitive API keys, which can lead to misuse of those keys and potential financial or reputational damage. The SSRF capability allows attackers to make the server send requests to internal systems, potentially exposing internal services or data that are not meant to be publicly accessible.

Detection Guidance

This vulnerability can be detected by checking for unauthenticated access to specific mem0 API endpoints that expose sensitive information or allow SSRF.

  • Send a GET request to /api/v1/config/ to see if LLM API keys are exposed in plaintext.
  • Send a PUT request to /api/v1/config/mem0/llm with a manipulated ollama_base_url parameter to test if SSRF is possible.

Example commands using curl:

  • curl -v http://<target-ip-or-host>/api/v1/config/
  • curl -v -X PUT http://<target-ip-or-host>/api/v1/config/mem0/llm -d '{"ollama_base_url":"http://169.254.169.254"}' -H 'Content-Type: application/json'
Mitigation Strategies

Immediate mitigation steps include restricting access to the vulnerable API endpoints and applying configuration changes to prevent exploitation.

  • Enforce authentication on all configuration API endpoints to prevent unauthenticated access.
  • Restrict the ollama_base_url parameter to approved URL schemes and IP address ranges to block SSRF attempts.
  • Avoid storing API keys in the configuration database or ensure they are encrypted and not exposed in plaintext.

Additionally, update mem0 to a version that includes fixes for this vulnerability once available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-59706. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart