Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-50027 – Authentication Bypass (Unauthenticated Read/Write/Delete) – mcp-memory-service < 10

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-50027 is a missing-authentication vulnerability (CWE-306) in mcp-memory-service, a Python-based memory storage server for the Model Context Protocol. The Document API endpoints under /api/documents/* are exposed without any authentication check, even when the server owner has configured an API key or OAuth. This flaw carries a CRITICAL CVSS v3.1 score of 9.8, as it allows a fully unauthenticated remote attacker to read, write, and delete stored memory data.

Technical details

  • Root cause: The documents.py router is instantiated without a router-level dependencies= parameter and does not import Depends, so no authentication dependency is applied to any route it defines.
  • Trigger conditions: The affected server exposes the Document API over the network; no credentials, session, or user interaction are required to reach the vulnerable routes, regardless of whether an API key or OAuth is configured for the rest of the application.
  • Attack vector: Network — an attacker sends unauthenticated HTTP requests directly to the exposed endpoints (POST /upload, POST /batch-upload, GET /history, GET /search-content/{upload_id}, DELETE /remove/{upload_id}, DELETE /remove-by-tags).
  • Impact: Confidentiality, integrity, and availability are all fully compromised — attackers can exfiltrate stored document content, inject arbitrary content into the memory store, and permanently delete legitimate stored memories. The parallel /api/memories endpoints correctly enforce authentication, making this an inconsistent authorization boundary specific to the Document API.

Affected software

  • doobidoo/mcp-memory-service versions prior to 10.67.1

Severity

  • CVSS v3.1 Base Score: 9.8 (CRITICAL)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade mcp-memory-service to version 10.67.1 or later, where authentication is enforced on the Document API endpoints.
  • If immediate patching is not possible: Restrict network exposure of the service (bind to localhost only or place it behind a network-level access control), and do not expose /api/documents/* routes to untrusted networks until patched.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: MCP Memory Service - Dashboard, MCP Memory Service v(version)

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge