CVE-2026-19325 in roo-code-memory-bank-mcp-server
Summary
by MITRE • 08/09/2026
A security vulnerability has been detected in IncomeStreamSurfer roo-code-memory-bank-mcp-server up to 9dcb2fb5e6b65a35ac1983885a6d4e5621a0081e. This affects the function readMemoryBankFile/appendMemoryBankEntry of the file src/index.ts of the component read_memory_bank_file/append_memory_bank_entry. Such manipulation of the argument file_name leads to path traversal. The attack must be carried out locally. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 08/09/2026
This vulnerability represents a critical path traversal flaw in the IncomeStreamSurfer roo-code-memory-bank-mcp-server software component, specifically within the readMemoryBankFile/appendMemoryBankEntry function located in src/index.ts. The vulnerability arises from insufficient input validation of the file_name argument, which allows malicious actors to manipulate the file path and access arbitrary files on the system through a directory traversal attack pattern. The issue is classified under CWE-22 as Path Traversal, where an attacker can traverse the file system hierarchy by manipulating directory navigation sequences in file paths.
The operational impact of this vulnerability is significant as it enables local privilege escalation attacks that can potentially lead to unauthorized access to sensitive data stored within the memory bank files. Attackers could exploit this flaw to read confidential information, modify critical system files, or even escalate privileges to gain administrative control over the affected system. Given that the attack vector requires local execution, the vulnerability primarily affects systems where untrusted users have access to the application's execution environment, making it particularly dangerous in multi-user or shared hosting scenarios.
The attack surface is limited to local exploitation only, meaning remote attackers cannot directly leverage this vulnerability from external networks. However, the risk remains elevated due to the rolling release deployment model used by the project, which makes it difficult to track specific vulnerable versions since version information is not publicly disclosed. This approach to continuous delivery creates challenges for security monitoring and patch management, as organizations cannot easily determine whether their installations are affected by known vulnerabilities.
Security practitioners should implement immediate mitigations including input sanitization of all file path parameters, implementing strict file access controls, and restricting local user privileges where possible. The vulnerability aligns with ATT&CK technique T1059.007 for command and scripting interpreter, as attackers might leverage this flaw to execute arbitrary code through manipulated file paths. Organizations should also establish proper monitoring of system logs for suspicious file access patterns and implement automated vulnerability scanning tools that can detect similar path traversal vulnerabilities across their infrastructure.
The lack of response from the project team following early issue reporting highlights potential security governance gaps in the software development lifecycle, particularly regarding vulnerability disclosure and remediation processes. This delay in addressing known security issues creates ongoing risk exposure for users who rely on this software component. The rolling release system itself may be contributing to the complexity of vulnerability management, as it prevents clear version-based identification of affected systems, making coordinated security response more challenging.
Organizations utilizing this software should consider implementing network segmentation and access controls to limit local execution privileges, while also establishing procedures for tracking and responding to security advisories in open source projects. The vulnerability demonstrates the importance of proper input validation and secure coding practices, particularly when dealing with file system operations that involve user-supplied data. Regular security assessments and penetration testing should be conducted to identify similar flaws in other components of the application stack.