CVE-2026-14611: DeepMyst Mysti Information Disclosure Flaw

CVE-2026-14611 Overview

CVE-2026-14611 is an information exposure vulnerability [CWE-200] affecting DeepMyst Mysti versions up to 0.4.0. The flaw resides in the initProjectMemory function within src/managers/MemoryManager.ts, part of the Per-Project Auto-Memory Handler component. Attackers can manipulate the workspacePath argument to trigger unintended exposure of resources across project boundaries. The issue stems from missing key isolation between project memory stores. Remote exploitation is possible, though authentication is required. The maintainers have published a fix in commit 6d709229b5199f6769fb3cf763e5122dcc43c079, which introduces a versioned project memory key schema.

Critical Impact
Authenticated remote attackers can manipulate workspace paths to access memory data belonging to other projects, exposing potentially sensitive contextual information stored by the auto-memory handler.

Affected Products

DeepMyst Mysti versions prior to 0.4.0
Component: Per-Project Auto-Memory Handler (src/managers/MemoryManager.ts)
Function: initProjectMemory

Discovery Timeline

2026-07-03 - CVE-2026-14611 published to NVD
2026-07-06 - Last updated in NVD database

Technical Details for CVE-2026-14611

Vulnerability Analysis

The vulnerability is classified as Information Exposure [CWE-200]. It affects the persistent memory subsystem of DeepMyst Mysti, which stores per-project context for autonomous operations. The initProjectMemory function accepts a workspacePath argument used to derive the storage key for a project's memory entries. Because the key derivation lacks proper namespace isolation, crafted or overlapping workspacePath values can cause one project to load memory entries associated with another. This exposes data that was intended to remain scoped to a single workspace.

Root Cause

The root cause is insufficient isolation of project memory keys within the MemoryManager module. Prior to the patch, the derivation logic did not enforce a schema-versioned, workspace-unique key. The maintainer fix introduces a PROJECT_MEMORY_KEY_SCHEMA constant set to mysti-project-memory-v2 and migrates legacy directories to the new format, ensuring each project's memory is stored under a distinct, schema-qualified key.

Attack Vector

Exploitation occurs over the network and requires low privileges. An authenticated actor supplies a manipulated workspacePath to the memory initialization routine. The routine then resolves storage under a colliding or predictable key, returning memory entries from an unrelated project. User interaction is not required. The scope is limited to information disclosure without direct impact on integrity or availability.

typescript

// Source: https://github.com/DeepMyst/Mysti/commit/6d709229b5199f6769fb3cf763e5122dcc43c079
// Patch in src/managers/MemoryManager.ts introducing versioned key schema
 const GLOBAL_STATE_KEY = 'mysti.autonomousMemory';
 const MEMORY_DIR_NAME = 'memory';
 const PROJECT_MEMORY_MAX_LINES = 200;
+const PROJECT_MEMORY_KEY_SCHEMA = 'mysti-project-memory-v2';
 
 interface MemoryStore {
   entries: MemoryEntry[];

The patch establishes a stable, versioned schema identifier used when deriving per-project storage keys. Combined with the legacy directory migration referenced in the commit message, this prevents key collisions between workspaces.

Detection Methods for CVE-2026-14611

Indicators of Compromise

Access to Mysti memory storage locations using workspacePath values that do not correspond to any legitimate project directory on the host.
Unexpected reads of the memory directory or global state key mysti.autonomousMemory from processes not associated with the owning workspace.
Cross-project memory entries appearing in logs when only one workspace should be active.

Detection Strategies

Audit Mysti application logs for calls to initProjectMemory referencing paths outside the expected workspace roots.
Compare stored project memory keys against the list of legitimate workspaces registered on the system.
Monitor filesystem access to the Mysti memory directory for reads originating from unexpected user contexts.

Monitoring Recommendations

Enable verbose logging for the MemoryManager module during and after upgrade to observe migration events.
Track version metadata to confirm memory stores are running under the mysti-project-memory-v2 schema.
Alert on repeated workspacePath parameter variations from the same authenticated session, which may indicate enumeration.

How to Mitigate CVE-2026-14611

Immediate Actions Required

Upgrade DeepMyst Mysti to version 0.4.0 or later, which contains the patch commit 6d709229b5199f6769fb3cf763e5122dcc43c079.
Review existing project memory stores for evidence of cross-project data and purge entries that cannot be attributed to a known workspace.
Restrict network access to Mysti instances so that only authorized authenticated users can invoke memory initialization.

Patch Information

The fix is delivered in DeepMyst Mysti 0.4.0. The patch, tracked as commit 6d709229b5199f6769fb3cf763e5122dcc43c079, introduces the PROJECT_MEMORY_KEY_SCHEMA constant and migrates legacy memory directories. Related maintainer discussion is available in the GitHub Pull Request and GitHub Issue Tracker. Additional advisory details are published on VulDB CVE Details.

Workarounds

If upgrading is not immediately possible, disable the Per-Project Auto-Memory Handler feature to prevent invocation of the vulnerable code path.
Enforce strict input validation on any external interface that supplies workspacePath to Mysti.
Segregate deployments so that only a single trusted workspace uses each Mysti instance until the patch is applied.

bash

# Upgrade DeepMyst Mysti to a fixed version
npm install mysti@0.4.0

# Verify the installed version contains the patched schema
grep -R "mysti-project-memory-v2" node_modules/mysti/src/managers/MemoryManager.ts