Categories
CVE-2026-33010

Vulnerability in mcp-memory-service (CVE-2026-33010)

Summary

Vulnerability in mcp-memory-service (CVE-2026-33010). Confidential information can be exposed externally. Exploitable via Origin. Mitigation: upgrade to 10.25.1 or later.

Original description

The description as published by the source.

Summary

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.

Details

Vulnerable Code

config.py:546 - Wildcard CORS origin default

CORS_ORIGINS = os.getenv('MCP_CORS_ORIGINS', '*').split(',')

This produces ['*'] by default, allowing any origin.

app.py:274-280 - CORSMiddleware configuration

# CORS middleware
app.add_middleware(
    CORSMiddleware,
    allow_origins=CORS_ORIGINS,        # ['*'] by default
    allow_credentials=True,             # Unnecessary for anonymous access; bad practice
    allow_methods=["*"],
    allow_headers=["*"],
)

How the Attack Works

The wildcard CORS default means every API response includes Access-Control-Allow-Origin: *. This tells browsers to allow any website to read the response. When combined with anonymous access (no authentication required), the attack is straightforward:

// Running on https://evil.com - reads victim's memories
// No credent…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-33010 has been found in mcp-memory-service.
Attackers can target a specific entry point like Origin over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade mcp-memory-service to 10.25.1 or later.
If unsure, ask your IT team or search "mcp-memory-service CVE-2026-33010" on the vendor's site.

CVE-2026-33010 (mcp-memory-service) — CWE-942
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Origin / OPTIONS / MCP_ALLOW_ANONYMOUS_ACCESS / api_key
Patched: 10.25.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-942) exists in mcp-memory-service. Attackers reach the vulnerable code path via Origin without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of mcp-memory-service. Attack surface: Origin / OPTIONS / MCP_ALLOW_ANONYMOUS_ACCESS / api_key.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 10.25.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mcp-memory-service' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'mcp-memory-service' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mcp-memory-service を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade mcp-memory-service to 10.25.1

    ステージング環境で 10.25.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI mcp-memory-service
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.25.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details