Executive brief
DeepMyst Mysti, an AI-driven coding assistant for VS Code, contains a vulnerability in how it manages project-specific memory. In shared development environments, the application fails to properly distinguish between different projects if they share the same file path. This could allow an unauthorized user to access or "poison" the memory and context of another project, potentially leading to the exposure of sensitive project information or influencing the AI's behavior.
Technical details
A resource exposure vulnerability exists in DeepMyst Mysti versions up to 0.4.0 within the `initProjectMemory` function of `MemoryManager.ts`. The vulnerability stems from the application deriving the memory namespace (storage key) directly from the literal workspace path string without canonicalization or unique identity markers. In shared development environments where different projects might occupy the same lexical path, a remote attacker with low privileges can cause their session to load another project's `MEMORY.md` file. This allows for the exposure of sensitive project context and potential cache poisoning of the AI agent's future context. The issue is addressed in version 0.4.0 by implementing a new canonical hash-based key schema (v2) for project memory isolation.
Affected products
- DeepMyst Mysti up to 0.4.0
Timeline
- 2026-06-01: disclosed: Issue reported on GitHub regarding project memory reuse.
- 2026-06-12: patched: Fix for project memory key isolation committed.
- 2026-07-03: advisory: CVE-2026-14611 published.