CVE-2026-43901: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in bx33661 Wireshark-MCP
Wireshark MCP is an MCP Server that turns tshark into a structured analysis interface, then layers in optional Wireshark suite utilities. In 1.1.5 and earlier, 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.
AI Analysis
Technical Summary
Wireshark-MCP (<= 1.1.5) contains a CWE-22 path traversal vulnerability in the wireshark_export_objects MCP tool. This tool passes a user-controlled dest_dir parameter to tshark's --export-objects flag without enforcing path restrictions. The default configuration does not enable the path sandbox (_allowed_dirs), which only activates if the WIRESHARK_MCP_ALLOWED_DIRS environment variable is set. Consequently, an attacker can specify arbitrary directories on the filesystem for export, potentially leading to unauthorized file writes. The vulnerability has a CVSS 3.1 base score of 6.8 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N), reflecting network attack vector, high attack complexity, no privileges required, user interaction needed, unchanged scope, and high confidentiality and integrity impact.
Potential Impact
Successful exploitation allows an attacker to write files to arbitrary directories on the filesystem where Wireshark-MCP is running. This can lead to unauthorized modification or creation of files, potentially compromising system integrity and confidentiality. The vulnerability does not affect availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently available. Users should consider setting the WIRESHARK_MCP_ALLOWED_DIRS environment variable to restrict export destinations to trusted directories, thereby enabling the path sandbox feature. Monitor vendor advisories for updates or official fixes. Until a fix is released, avoid running Wireshark-MCP in environments where untrusted users can control the dest_dir parameter.
CVE-2026-43901: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in bx33661 Wireshark-MCP
Description
Wireshark MCP is an MCP Server that turns tshark into a structured analysis interface, then layers in optional Wireshark suite utilities. In 1.1.5 and earlier, 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.
CVSS v3.1
Score 6.8medium
Affected software
pkg:github/bx33661/Wireshark-MCPRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Wireshark-MCP (<= 1.1.5) contains a CWE-22 path traversal vulnerability in the wireshark_export_objects MCP tool. This tool passes a user-controlled dest_dir parameter to tshark's --export-objects flag without enforcing path restrictions. The default configuration does not enable the path sandbox (_allowed_dirs), which only activates if the WIRESHARK_MCP_ALLOWED_DIRS environment variable is set. Consequently, an attacker can specify arbitrary directories on the filesystem for export, potentially leading to unauthorized file writes. The vulnerability has a CVSS 3.1 base score of 6.8 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N), reflecting network attack vector, high attack complexity, no privileges required, user interaction needed, unchanged scope, and high confidentiality and integrity impact.
Potential Impact
Successful exploitation allows an attacker to write files to arbitrary directories on the filesystem where Wireshark-MCP is running. This can lead to unauthorized modification or creation of files, potentially compromising system integrity and confidentiality. The vulnerability does not affect availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently available. Users should consider setting the WIRESHARK_MCP_ALLOWED_DIRS environment variable to restrict export destinations to trusted directories, thereby enabling the path sandbox feature. Monitor vendor advisories for updates or official fixes. Until a fix is released, avoid running Wireshark-MCP in environments where untrusted users can control the dest_dir parameter.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-04T16:11:33.085Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a028743cbff5d86108b506e
Added to database: 05/12/2026, 01:49:55 UTC
Last enriched: 05/19/2026, 09:38:13 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 79
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.