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

Advisory record · `GHSA-3r68-x3xc-rxpg`

- **Identifiers:** `GHSA-3r68-x3xc-rxpg` · `CVE-2026-43901` · `PYSEC-2026-3426`
- **State:** Confirmed
- **Severity:** CVSS 6.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 5 May 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 May 2026, 20:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wireshark-mcp` (PyPI): affected `<=1.1.5`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The wireshark-mcp package, versions up to and including 1.1.5, lets the wireshark_export_objects tool write files to any directory unless the WIRESHARK_MCP_ALLOWED_DIRS environment variable is set, since the path restriction is off by default. An attacker who can get a crafted pcap processed, for example through prompt injection of an AI model using the server, could cause arbitrary files to be written, which the source says could grant SSH access. No fix is listed; the workaround is to set WIRESHARK_MCP_ALLOWED_DIRS to a restricted directory.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 28th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:01 UTC: First seen by agentprime
- 31 Oct 2026, 15:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3r68-x3xc-rxpg)

## Sources

- [GitHub Advisory Database: GHSA-3r68-x3xc-rxpg](https://github.com/advisories/GHSA-3r68-x3xc-rxpg)
- [OSV: GHSA-3r68-x3xc-rxpg](https://osv.dev/vulnerability/GHSA-3r68-x3xc-rxpg)
- <https://github.com/bx33661/Wireshark-MCP/security/advisories/GHSA-3r68-x3xc-rxpg>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-43901>
- <https://github.com/bx33661/Wireshark-MCP>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3r68-x3xc-rxpg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3r68-x3xc-rxpg/>. Everything for agents: <https://agentprime.io/llms.txt>.
