# CVE-2026-50027: mcp-memory-service: Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Delete

> Unauthenticated attackers can read, write, and delete memory documents in mcp-memory-service due to missing authentication on specific API endpoints.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-84hp-mqvj-3p8h, PYSEC-2026-2624

## What is CVE-2026-50027?

CVE-2026-50027 is a critical missing authorization vulnerability in doobidoo mcp-memory-service, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mcp-memory-service is a semantic memory layer for AI applications. Prior to 10.67.1, all HTTP routes under /api/documents/* in mcp-memory-service are served without any authentication dependency, even when the server is configured with an API key (MCP_API_KEY) or OAuth. An unauthenticated remote attacker can upload arbitrary content into the memory store (write), retrieve stored document content (read), and permanently delete memories belonging to authenticated users (delete) — all without supplying any credentials. The /api/memories counterpart correctly enforces authentication, making this an inconsistent and exploitable authentication boundary. This vulnerability is fixed in 10.67.1.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-50027?

3 open source packages ship an affected version, including mcp-memory-service.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mcp-memory-service` | PyPI | All versions | 10.67.1 |
| `mcp-memory-service` | PyPI | All versions | 10.67.1 |
| `mcp-memory-service` | PyPI | All versions | 10.67.1 |

## How do I fix CVE-2026-50027?

Upgrade mcp-memory-service to 10.67.1 or later.

## Is CVE-2026-50027 being exploited?

There is no known exploitation of CVE-2026-50027 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50027 and fix it if it is affected.

What it is: CVE-2026-50027 is a critical missing authorization vulnerability in doobidoo mcp-memory-service, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50027 in the wild and no public exploit code.

Affected packages and fixed versions:
- mcp-memory-service (PyPI): affected all versions; fixed in 10.67.1
- mcp-memory-service (PyPI): affected all versions; fixed in 10.67.1
- mcp-memory-service (PyPI): affected all versions; fixed in 10.67.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50027/ (Markdown: https://insights.sbomify.com/CVE-2026-50027/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50027
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50027
- OSV: https://osv.dev/vulnerability/CVE-2026-50027

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50027/
Summaries are generated and may contain mistakes; the official description above is the record.