Path Traversal in wireshark-mcp (CVE-2026-43901)
Summary
Path traversal in wireshark-mcp (CVE-2026-43901). Confidential information can be exposed externally. Exploitable via wireshark_export_objects.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-43901 has been found in wireshark-mcp.
Attackers can target a specific entry point like wireshark_export_objects over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wireshark-mcp CVE-2026-43901" on the vendor's site.
CVE-2026-43901 (wireshark-mcp) — CWE-22 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: wireshark_export_objects / dest_dir / _allowed_dirs / None
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in wireshark-mcp. Attackers reach the vulnerable code path via wireshark_export_objects without authentication.
Check the vendor advisory for the affected versions of wireshark-mcp. Attack surface: wireshark_export_objects / dest_dir / _allowed_dirs / None.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wireshark-mcp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wireshark-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wireshark-mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-43901 wireshark
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com