dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-59706

CRITICAL · 9.3 CVSS v3.1 Published 2026-07-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

mem0 has unauthenticated API endpoints at GET /api/v1/config/ and PUT /api/v1/config/mem0/llm that expose LLM API keys in plaintext and allow SSRF via the attacker-controlled ollama_base_url parameter, enabling retrieval of stored secrets like OpenAI keys and internal network access.

MitigationImmediately restrict /api/v1/config/* endpoints to authenticated users only, encrypt stored API keys at rest, implement strict URL validation to prevent SSRF by blocking internal addresses, and rotate any exposed credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify unauthenticated access to /api/v1/config/
    Send a GET request to http://<host>/api/v1/config/ without any authentication headers or tokens. Inspect the response status and body.
    Affected if The endpoint returns a 200 OK response with configuration data containing plaintext API keys (e.g., OpenAI, Anthropic keys) without requiring authentication.
  2. Test PUT endpoint for unauthenticated LLM config modification
    Send a PUT request to http://<host>/api/v1/config/mem0/llm with a JSON body containing an ollama_base_url parameter, without any authentication headers. Observe if the request is accepted.
    Affected if The endpoint accepts the request without authentication and returns 200 OK, allowing configuration changes.
  3. Check for SSRF via ollama_base_url parameter
    Send a PUT request to /api/v1/config/mem0/llm with ollama_base_url set to an internal address (e.g., http://localhost:8080, http://169.254.169.254) and check if the server attempts to connect to it.
    Affected if The server accepts arbitrary URLs in ollama_base_url without validation and attempts to connect to internal/private network addresses.
  4. Inspect API key storage for plaintext exposure
    Examine the application's configuration files, environment variables, or database storage where LLM API keys are stored. Check if they appear in plaintext rather than being encrypted or masked.
    Affected if API keys for LLM providers (OpenAI, Anthropic, etc.) are stored and returned in plaintext within the config endpoint response.
  5. Confirm network exposure of vulnerable endpoints
    Determine if the mem0 API server is bound to 0.0.0.0 or a public IP address rather than localhost only. Check firewall rules and reverse proxy configurations.
    Affected if The /api/v1/config/* endpoints are accessible from external network addresses rather than being restricted to localhost or authenticated proxies.

You are affected if the /api/v1/config/ endpoints are accessible without authentication and return plaintext API keys, or if arbitrary URLs are accepted in the ollama_base_url parameter enabling SSRF attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Immediately restrict /api/v1/config/* endpoints to authenticated users only, encrypt stored API keys at rest, implement strict URL validation to prevent SSRF by blocking internal addresses, and rotate any exposed credentials.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59706 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59706 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data