Skip to main content
VulnerabilityPublished Updated

CVE-2026-43901: bx33661 Wireshark-MCP · Path Traversal

Affects bx33661 Wireshark-MCPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
bx33661Wireshark-MCPAffected
  • <=1.1.5
Fixed in–
GitHubbx33661/Wireshark-MCPpkg:github/bx33661/Wireshark-MCPOther threatsAffected
  • <=1.1.5
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…