# CVE-2026-33010: mcp-memory-service's Wildcard CORS with Credentials Enables Cross-Origin Memory Theft

> Misconfigured CORS allows malicious websites to read, modify, and delete stored memories in mcp-memory-service when HTTP and anonymous access are enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-g9rg-8vq5-mpwm, PYSEC-2026-2625

## What is CVE-2026-33010?

CVE-2026-33010 is a high-severity vulnerability in doobidoo mcp-memory-service, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

mcp-memory-service is an open-source memory backend for multi-agent systems. Prior to version 10.25.1, when the HTTP server is enabled (MCP_HTTP_ENABLED=true), the application configures FastAPI's CORSMiddleware with allow_origins=['*'], allow_credentials=True, allow_methods=["*"], and allow_headers=["*"]. The wildcard Access-Control-Allow-Origin: * header permits any website to read API responses cross-origin. When combined with anonymous access (MCP_ALLOW_ANONYMOUS_ACCESS=true) - the simplest way to get the HTTP dashboard working without OAuth - no credentials are needed, so any malicious website can silently read, modify, and delete all stored memories. This issue has been patched in version 10.25.1.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

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

3 open source packages ship an affected version, including mcp-memory-service. It affects 1 product.


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

Products: Doobidoo Mcp-Memory-Service.

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

Upgrade mcp-memory-service to 10.25.1 or later.

## Is CVE-2026-33010 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33010 exists.

## Other vulnerabilities in doobidoo mcp-memory-service

- [CVE-2026-29787](https://insights.sbomify.com/CVE-2026-29787/): mcp-memory-service: System Information Disclosure via Health Endpoint (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33010 is a high-severity vulnerability in doobidoo mcp-memory-service, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33010 exists.

Affected packages and fixed versions:
- mcp-memory-service (PyPI): affected all versions; fixed in 10.25.1
- mcp-memory-service (PyPI): affected all versions; fixed in 10.25.1
- mcp-memory-service (PyPI): affected all versions; fixed in 10.25.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-33010/ (Markdown: https://insights.sbomify.com/CVE-2026-33010/index.md)
```

## Sources

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

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