CVE-2026-114497 in codebase-memory-mcp
Summary
by MITRE • 11/20/2026
codebase-memory-mcp provides local code intelligence for developers and AI agents through a persistent graph and MCP tools. Prior to 0.9.1-rc.1, the optional graph UI's POST /api/process-kill route omitted the indexing-job ownership check on Windows while retaining that check on POSIX systems. A requester able to reach the optional UI could supply an arbitrary process identifier, causing TerminateProcess to stop any process that the server user was permitted to terminate. The flaw affects the Windows-specific process termination path and can cause a high availability impact without disclosing or modifying data. This issue is fixed in version 0.9.1-rc.1.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified within codebase-memory-mcp prior to version 0.9.1-rc.1 represents a critical authorization bypass rooted in inconsistent security controls across operating system platforms. The software provides local code intelligence through a persistent graph and Model Context Protocol tools, including an optional graphical user interface for managing operations. A specific endpoint, POST /api/process-kill, was designed to allow the termination of background indexing jobs that support these intelligence features. While this functionality is necessary for operational management, it requires strict access control to prevent abuse by unauthorized or malicious actors who might gain access to the UI layer.
The core technical flaw lies in a platform-specific inconsistency within the server's implementation logic. On POSIX-compliant systems such as Linux and macOS, the endpoint correctly enforced an ownership check, ensuring that only the user who initiated a specific indexing job could request its termination. However, on Windows platforms, this critical validation step was omitted entirely from the code path handling process termination requests. This discrepancy means that any actor capable of sending HTTP POST requests to the /api/process-kill route on a Windows system can bypass authentication and authorization mechanisms intended to restrict access based on job ownership.
From an operational perspective, this flaw allows for significant denial-of-service impacts against local infrastructure. An attacker with network or interface access to the optional UI could supply arbitrary process identifiers as part of their request payload. The server would then invoke the Windows API function TerminateProcess using these unvalidated inputs. This capability enables the termination of any running process that the user account executing the codebase-memory-mcp service has permission to kill, regardless of whether those processes are related to the application's internal indexing jobs or other critical system services.
The security implications extend beyond simple availability disruption. By allowing arbitrary process termination, the vulnerability effectively grants an attacker a mechanism for privilege escalation and resource exhaustion within the context of the compromised user account. This aligns with CWE-284, which describes Improper Access Control, specifically highlighting failures in verifying authorization before performing actions that affect system stability or data integrity. Furthermore, this behavior maps to MITRE ATT&CK technique T1529, System Shutdown/Reboot, as well as aspects of T1073, Application Window Discovery, if the attacker uses the process list for reconnaissance prior to termination.
The impact is characterized by high availability risk without direct data disclosure or modification at this stage. The primary consequence is the disruption of services running under the same user context, potentially leading to system instability, loss of ongoing work, and degradation of local development environments that rely on continuous indexing operations. While no sensitive data is directly exfiltrated through this specific vector, the ability to disrupt critical processes can indirectly lead to data loss if unsaved work in other applications is terminated abruptly.
To mitigate this vulnerability, organizations must upgrade codebase-memory-mcp to version 0.9.1-rc.1 or later, where the Windows-specific process termination path has been corrected to include proper ownership verification consistent with POSIX implementations. Until an update can be applied, administrators should restrict network access to the optional UI interface using firewall rules or reverse proxy configurations that enforce strong authentication and authorization policies at a higher layer. Additionally, running the service under a least-privilege account with restricted permissions to terminate system processes can reduce the blast radius of any successful exploitation attempt by limiting which process identifiers are valid targets for termination commands.