CVE-2026-114497
codebase-memory-mcp Windows UI could terminate unrelated processes
DeusData · codebase-memory-mcp
First documented disclosure · Review checkpoint
Summary
The optional graph UI could kill a PID it did not own.
Severity and exploitation evidence
Medium · 5.5/10 · CVSS 3.1. Severity source.
Exploitation not established: Public evidence describes a weakness, source correction or controlled demonstration; malicious exploitation against users is not established.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The Windows process-kill branch omits the indexing-job ownership check present on POSIX.
Conditions required
Windows with optional UI enabled and an attacker able to reach the endpoint.
Potential impact
Terminate processes that the server user can stop; availability impact only.
Affected versions and configurations
Native/npm before 0.9.1-rc.1; PyPI before 0.10.0.
Fix and mitigation status
Native/npm0.9.1-rc.1; first verified stable PyPI0.10.0. Recommended0.12.1.
Practical next steps
Upgrade all distributions to 0.12.1 or later; disable the optional UI on affected Windows systems.
Operating lesson
Check target ownership consistently across platforms.
Evidence and limits
The route was removed. Host-header changes in 0.9.0 did not fix PID ownership. Do not rely on historical PyPI prerelease delivery; CNA generic range omits this packaging distinction. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 3.1 5.5.
Sources
- GitHub_M CVE authority record
Primary source ·
- codebase-memory-mcp original advisory
Primary source ·
- Public corrective change
Primary source ·