p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de mcp-memory-service

Vulnérabilité publiée pour mcp-memory-service au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 4

  1. CVE-2026-50027

    Critique · CVSS 9.8EPSS 0,96%Correctif disponible

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

    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 boun

    • Mettez à jour vers 10.67.1
    Publication Mise à jour
  2. CVE-2026-49291

    Élevée · CVSS 8.1EPSS 0,49%Correctif disponible

    mcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/call

    mcp-memory-service is a semantic memory layer for AI applications. Prior to version 10.65.3, the HTTP MCP JSON-RPC endpoint at `/mcp` requires only OAuth `read` scope for all requests, then dispatches `tools/call` directly to handlers that include mutating tools. A read-only OAuth client can call `store_memory` and `delete_memory` through MCP even though the corresponding REST endpoints require `write` scope. Version 10.65.3 patches the issue.

    • Mettez à jour vers 10.65.3
    Publication Mise à jour
  3. CVE-2026-33010

    Élevée · CVSS 8.1EPSS 0,39%Correctif disponible

    mcp-memory-service's Wildcard CORS with Credentials Enables Cross-Origin Memory Theft

    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 st

    • Mettez à jour vers 10.25.1
    Publication Mise à jour
  4. CVE-2026-29787

    Moyenne · CVSS 5.3EPSS 0,38%Correctif disponible

    mcp-memory-service: System Information Disclosure via Health Endpoint

    mcp-memory-service is an open-source memory backend for multi-agent systems. Prior to version 10.21.0, the /api/health/detailed endpoint returns detailed system information including OS version, Python version, CPU count, memory totals, disk usage, and the full database filesystem path. When MCP_ALLOW_ANONYMOUS_ACCESS=true is set (required for the HTTP server to function without OAuth/API key), this endpoint is accessible without authentication. Combined with the default 0.0.0.0 binding, this exposes sensitive reconnaissance data to the entire network. This issue has been patched in version 10.21.0.

    • Mettez à jour vers 10.21.0
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →