CVE-2026-14611 DeepMyst CVE debrief

Who should care

Defenders responsible for DeepMyst Mysti deployments should assess exposure and verify the version in use. They should prioritize upgrading to version 0.4.0 or later and review custom modifications to the initProjectMemory function.

Why it matters

CVE-2026-14611 is a medium-severity vulnerability in DeepMyst Mysti's Per-Project Auto-Memory Handler, allowing for remote resource exposure. Defenders should verify the version in use, upgrade to 0.4.0 or later, and review custom modifications to the affected function.

• Verify version of DeepMyst Mysti in use.
• Upgrade to version 0.4.0 or later if vulnerable.
• Review custom modifications to initProjectMemory function.

Technical summary

The DeepMyst Mysti component's Per-Project Auto-Memory Handler, specifically the initProjectMemory function in src/managers/MemoryManager.ts, is vulnerable to resource exposure. This can occur through manipulation of the workspacePath argument and can be performed remotely. The issue is addressed in version 0.4.0 with patch 6d709229b5199f6769fb3cf763e5122dcc43c079. Defenders should prioritize verifying the version of DeepMyst Mysti in use and upgrading to version 0.4.0 or later if vulnerable. They should also review the initProjectMemory function in src/managers/MemoryManager.ts for any custom modifications that could affect the fix.

Defensive priority

Defenders should prioritize verifying the version of DeepMyst Mysti in use and upgrading to version 0.4.0 or later if vulnerable. They should also review the initProjectMemory function in src/managers/MemoryManager.ts for any custom modifications that could affect the fix.

Recommended defensive actions

• Verify the version of DeepMyst Mysti in use and upgrade to version 0.4.0 or later if vulnerable.
• Review the initProjectMemory function in src/managers/MemoryManager.ts for any custom modifications that could affect the fix.
• Monitor for any remote manipulation of the workspacePath argument in the Per-Project Auto-Memory Handler.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions beyond 0.4.0, exploitation, impact, or remediation beyond upgrading to 0.4.0.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.