Loading story…
A critical command injection flaw in SepineTam's mcp-for-stata exposed the stata_do API and CLI to remote code execution by interpolating the user-controlled log_file_name parameter directly into a Stata command string without sanitization. The issue reportedly affects versions through v1.17.2 and impacts both Unix-like and Windows execution paths in src/stata_mcp/stata/stata_do/do.py. Researchers said the project's GuardValidator did not stop the attack because it inspected only do-file content, not wrapper parameters, allowing attackers to inject Stata commands such as shell, python, or erase and potentially execute host-level commands.
The vulnerability also introduced a path traversal risk because crafted log names could escape the intended log directory and overwrite arbitrary files. A GitHub advisory and issue report included proof-of-concept abuse showing a malicious log_file_name could trigger shell execution and write to files such as /tmp/pwned.txt, while warning that dofile_path may carry similar injection risk because it is also embedded in a command string. A subsequent fix added regex-based validation for log_file_name, restricted names to 1-128 characters from a safe allowlist, blocked empty path components and . or .., and moved log path generation into a helper function, though the Windows code path still retains shell=True for Stata startup and path resolution.
See real exploitation activity before you spend the cycle.
2 events from the most recent confirmed update back to the earliest known activity.
A code commit added regex-based validation for log_file_name, restricted it to a safe character set and length, and blocked empty path components plus '.' and '..'. The change also routed log path creation through a helper method instead of directly interpolating the filename into command construction.
A GitHub issue and advisory disclosed a command injection vulnerability in the stata_do API and CLI, where the user-controlled log_file_name parameter was interpolated into a Stata command string without sanitization. The report said the flaw affected versions up to v1.17.2 and could enable remote code execution and path traversal.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
4 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Researchers disclosed multiple security flaws affecting AWS MCP components, including a local file inclusion bug in the AWS Remote MCP Server and a critical command injection issue in `aws-mcp-server`. Varonis said authenticated users could abuse AWS CLI shorthand syntax, specifically the `@=` operator passed through the `aws___call_aws` tool, to read arbitrary files from the underlying host even when `FileAccessMode=NO_ACCESS` was enabled. AWS assigned **CVE-2026-4270** to the file access restriction bypass and said the issue was fixed in `aws-api-mcp-server` version **1.3.9**; the exposure affected the public endpoint `aws-mcp.us-east-1.api.aws` as well as self-hosted or forked deployments. A separate flaw, tracked as **CVE-2026-5058** and published by Trend Micro's Zero Day Initiative as **ZDI-26-246**, allows unauthenticated remote code execution in `aws-mcp-server` because user-supplied input in the allowed-commands list is not properly validated before being used in a system call. ZDI rated the bug **CVSS 9.8** and said successful exploitation lets attackers run arbitrary code in the MCP server context; the advisory was released as a 0-day after the vendor rejected the report. The disclosures landed alongside another AWS bulletin for **CVE-2026-4269**, an improper S3 ownership verification issue in the Bedrock AgentCore Starter Toolkit, underscoring broader security concerns around MCP-related tooling and the need for immediate patching and review of derivative implementations.
Jun 29, 2026
CERT Polska disclosed four vulnerabilities in **Logseq** affecting releases through `0.10.15`, including an **OS command injection** flaw, an exposed dangerous function that permits arbitrary file operations, a **stored XSS** issue in plugin metadata, and a **sandbox escape** that can lead to privileged JavaScript execution. The vulnerabilities were reported by Bartłomiej Dmitruk of striga.ai and published after coordinated disclosure. The issues can be chained so that an attacker who gains JavaScript execution in the renderer—through stored XSS or a malicious plugin—can escalate to **arbitrary shell command execution** or unauthorized access to files on the host system. CERT Polska said `v0.10.15` was tested and confirmed vulnerable for one issue, while the status of other versions remained unclear because the vendor had not yet addressed the problems.
Jun 29, 2026
Anthropic fixed three vulnerabilities in its official *Git MCP server* (`mcp-server-git`) that could be triggered via **prompt injection** and chained with other MCP tools to achieve **remote code execution** or destructive file operations. The issues were reported by agentic AI security firm **Cyata**, which demonstrated that attacker-controlled content an AI assistant might read (for example, a malicious `README`, poisoned issue text, or other untrusted context) could drive the LLM to invoke MCP tool calls with crafted arguments, enabling exploitation without the attacker having direct access to the victim host. Cyata identified `CVE-2025-68143` (**unrestricted `git_init`**), `CVE-2025-68145` (**path validation bypass**), and `CVE-2025-68144` (**argument injection in `git_diff`**). In combination—particularly when `mcp-server-git` is used alongside the *Filesystem MCP server*—the flaws could enable code execution, arbitrary file deletion/overwrite, and reading arbitrary files into the LLM context (with Cyata noting this does not inherently provide direct exfiltration). The vulnerabilities affected default deployments of `mcp-server-git` prior to **version `2025.12.18`**; Anthropic was notified in June and shipped fixes in December, and there was no indication reported that the bugs were exploited in the wild.
Jun 29, 2026