CVE-2026-5619
OS Command Injection in Braffolk mcp-summarization-functions summarize_command
Publication date: 2026-04-06
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| braffolk | mcp-summarization-functions | to 0.1.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-5619 is a command injection vulnerability found in Braffolk mcp-summarization-functions up to version 0.1.5. It occurs in the summarize_command component, specifically in the file src/server/mcp-server.ts. The vulnerability arises because the argument 'command' is not properly sanitized before being passed to the operating system's command execution function, allowing an attacker to execute arbitrary OS commands.
An attacker with local access can manipulate the 'command' argument to inject malicious commands. This flaw is classified under CWE-78, which involves improper neutralization of special elements used in OS commands. The vulnerability allows execution of arbitrary shell commands with the privileges of the server process.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including full host compromise. An attacker exploiting this flaw can execute arbitrary system commands, potentially leading to exposure of sensitive data, alteration of server state, and disruption of services.
- Confidentiality impact: possible exposure of host or system data.
- Integrity impact: unauthorized changes to server state or data.
- Availability impact: disruption or denial of service to legitimate users.
Additionally, if Server-Side Request Forgery (SSRF) is possible, the attacker could exploit the server's network to reach internal or attacker-chosen targets, increasing the scope of the attack.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to invoke the vulnerable MCP/HTTP endpoint with crafted JSON-RPC requests that include the "summarize_command" tool and a command argument designed to execute arbitrary shell commands.
A proof of concept involves sending a JSON-RPC request with a command argument such as "echo vulnerable; id;" to check if arbitrary commands are executed on the server.
Detection commands could include using curl or similar tools to send such JSON-RPC requests to the MCP/HTTP interface, for example:
- curl -X POST http://<target-server>/mcp -H 'Content-Type: application/json' -d '{"method":"summarize_command","params":{"command":"echo vulnerable; id;"}}'
If the response includes output from the executed shell commands (e.g., user id information), it indicates the presence of the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include removing or disabling the direct execution of shell commands from user-supplied input in the vulnerable MCP/HTTP request paths.
Replace free-form command arguments with fixed allowlists and validated argument schemas to prevent injection of arbitrary commands.
Prefer using argument-array process execution methods that do not invoke a shell interpreter, thereby avoiding command injection.
Add authentication, authorization, logging, and rate limiting on sensitive MCP/HTTP handlers to reduce the attack surface.
Implement input schema validation at MCP/HTTP boundaries to ensure attacker-controlled values cannot reach command execution sinks.
Monitor for patches or security advisories from the vendor or maintainers and apply updates once available.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows an attacker to execute arbitrary system commands on the affected server, potentially leading to full host compromise including data exposure, integrity loss, and service disruption.
Such impacts on confidentiality, integrity, and availability of data could lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and system integrity.
Specifically, unauthorized data exposure or alteration caused by this vulnerability could violate data protection requirements, while service disruption could affect availability obligations.