Wireshark MCP's export_objects tool accepts an attacker‑controlled destination directory and forwards it to tshark’s --export-objects flag without enforcing any path restrictions. This capability allows an attacker to write files to any location on the host filesystem, resulting in arbitrary file overwrite or creation. The vulnerability aligns with CWE‑22, where directory traversal or lack of proper checks permits untrusted inputs to produce unintended file system access.

The affected product is Wireshark‑MCP (bx33661) version 1.1.5 and earlier. In a default installation the allowed‑dirs sandbox is disabled unless the environment variable WIRESHARK_MCP_ALLOWED_DIRS is set, meaning any user with access to the MCP server could target arbitrary directories on the host system.

The CVSS score of 6.8 indicates a medium severity. Because the EPSS score is not available, the current exploitation probability is unknown, but the vulnerability is not listed in the CISA KEV catalog. An attacker who can communicate with the MCP server can exploit the flaw remotely by sending a crafted dest_dir parameter; successful exploitation grants write access to sensitive files or the ability to create malicious files, potentially leading to privilege escalation or persistence. The lack of a mandatory path restriction makes the attack straightforward, but the impact depends on the privileges of the MCP process and the configuration of the host.