Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-59706 – Unauthenticated Secret Disclosure and SSRF – mem0 OpenMemory (all versions throu…

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-59706 is a critical vulnerability (CVSS 9.2) caused by missing authentication on configuration API endpoints in mem0’s OpenMemory self-hosted REST API server. Two distinct unauthenticated attack paths allow remote attackers to retrieve stored LLM API keys in plaintext and conduct server-side request forgery (SSRF) against internal infrastructure — including cloud metadata services. No authentication or user interaction is required to exploit either path.

Technical details

  • Root cause: Missing authentication on configuration API endpoints in openmemory/api/app/routers/config.py (CWE-306: Missing Authentication for Critical Function). The /api/v1/config/ endpoints are publicly reachable with no credential check enforced.
  • Attack path 1 — Credential disclosure: A GET /api/v1/config/ request returns the full LLM configuration in plaintext — including stored API keys such as OpenAI API keys — to any unauthenticated caller.
  • Attack path 2 — SSRF: A PUT /api/v1/config/mem0/llm request accepts an attacker-supplied ollama_base_url parameter with no URL scheme or IP-range validation. By supplying an internal address (e.g., http://169.254.169.254/latest/meta-data/ for cloud IMDS), an attacker can force the server to issue HTTP requests to internal infrastructure and retrieve cloud provider credentials or other sensitive internal metadata.
  • Attack vector: Network (AV:N); no authentication required (PR:N); no user interaction required (UI:N).
  • Impact: High confidentiality impact on both the directly compromised system (VC:H — LLM API key theft) and on subsequent systems (SC:H — potential cloud infrastructure credential access via IMDS pivot).

Affected software

  • mem0 (OpenMemory): All versions up to and including commit a3154d5

Severity

  • CVSS v4.0: 9.2 (Critical) — 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
  • CVSS v3.1: 9.3 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Mitigation and recommended actions

  • Patch: Update mem0 to a version that includes the fix beyond commit a3154d5. Refer to the official mem0 GitHub repository for the latest patched release.
  • Network isolation: If immediate patching is not feasible, restrict all external access to the mem0 REST API server at the network perimeter. The server should not be directly internet-facing.
  • SSRF hardening: Block outbound HTTP requests from the mem0 host to link-local and private IP ranges (e.g., 169.254.169.254, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) at the host firewall or cloud security group level.
  • Credential rotation: Any LLM API keys (e.g., OpenAI API keys) stored in a mem0 instance that may have been internet-exposed should be treated as compromised and rotated immediately.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge