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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.8 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N | 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