This weekExploitable · Confirmed
wireshark-mcp: wireshark-mcp vulnerable to arbitrary file write via export_objects when WIRESHARK_MCP_ALLOWED_DIRS is not configured
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
wireshark-mcp (PyPI)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- wireshark-mcp (PyPI): every version, up to and including 1.1.5
- wireshark-mcp (PyPI): every version, up to and including 1.1.5
The fix
No fix yet: isolate it or follow the vendor's mitigation.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))