CVE-2026-50027

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

July 2, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Sep 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

GitHub - doobidoo/mcp-memory-service: Open-source persistent memory for AI agent pipelines (LangGraph, CrewAI, AutoGen) and Claude. REST API + knowledge graph + autonomous consolidation. · GitHub

https://web.archive.org/web/20260508112116/https://github.com/doobidoo/mcp-memory-service
generic

Client Challenge

https://pypi.org/project/mcp-memory-service
github Patch Available🟡 PoC Available

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

https://github.com/advisories/GHSA-84hp-mqvj-3p8h

Vendor Advisories for CVE-2026-50027(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mcp-memory-service10.0.0 ... 9.3.1 (293 versions)10.67.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 14:20 UTCEG score recompute
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-05 23:55 UTCEG score recompute
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 20:47 UTCEG score recompute
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 11:24 UTCEG score recompute
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 22:16 UTCEG score recompute
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 20:56 UTCEG score recompute
  22. 2026-08-24 10:20 UTCEG score recompute
  23. 2026-08-23 03:19 UTCEG score recompute
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-22 00:59 UTCEG score recompute
Show 18 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-20 23:58 UTCEG score recompute
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 04:14 UTCEG score recompute
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 20:55 UTCEG score recompute
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 15:03 UTCEG score recompute
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 19:44 UTCEG score recompute
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 03:19 UTCEG score recompute
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-14 19:36 UTCEG score recompute
  15. 2026-07-30 09:34 UTCEG score recompute
  16. 2026-07-26 13:06 UTCEG score recompute
  17. 2026-07-23 03:18 UTCEG score recompute
  18. 2026-07-02 16:24 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50027?
CVE-2026-50027 is a critical vulnerability published on July 2, 2026. 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 (MCPAPIKEY) or OAuth. An unauthenticated remote…
When was CVE-2026-50027 disclosed?
CVE-2026-50027 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50027 actively exploited?
CVE-2026-50027 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.6% of all scored CVEs.
What is the CVSS score of CVE-2026-50027?
CVE-2026-50027 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-50027?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50027, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50027

Explore →

Is Your Infrastructure Affected by CVE-2026-50027?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs