UTC
Medium

wireshark-mcp vulnerable to arbitrary file write via export_objects when WIRESHARK_MCP_ALLOWED_DIRS is not configured

CVE-2026-43901 · GHSA-3r68-x3xc-rxpg · published 2026-05-05 · updated 2026-05-13

Severity
Medium
CVSS score
6.8
Chance of exploitation (EPSS)
0.34%
Fixed in
No fix yet
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

wireshark-mcp exposes a wireshark_export_objects MCP tool that accepts an attacker-controlled dest_dir parameter and passes it to tshark's --export-objects flag with no mandatory path restriction. The path sandbox (_allowed_dirs) is None by default and only activates when the environment variable WIRESHARK_MCP_ALLOWED_DIRS is explicitly set. In a default installation, any directory on the filesystem can be used as the export destination.

What to do

No fixed release is listed yet for wireshark-mcp. Follow the source advisory for updates, and until one ships:

From the advisory (GitHub Advisory Database, CC BY 4.0)
Set WIRESHARK_MCP_ALLOWED_DIRS to a restricted safe directory before starting the server: export WIRESHARK_MCP_ALLOWED_DIRS=/tmp/wireshark_mcp_safe This activates the existing sandbox and blocks writes outside the allowed path.

The full advisory →Licence

General guidance from ShieldPi, not a vendor fix

  • Path traversal. Limit the folders it can reach at the operating-system level, such as a container or a user with access to only those folders, and keep credentials and keys outside them.

Not yet patched.

Affected
PackageRegistryAffectedFixed in
wireshark-mcpPyPI<= 1.1.5No fix yet
Downstream in the Official MCP Registry

1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.

  • io.github.bx33661/wireshark-mcpwireshark-mcp@0.6.5
See the trace →

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].