Wireshark sharkd EUVD-2026-26313

Upgrade Wireshark and sharkd to a patched release outside the affected version ranges-recommended is the latest stable version of the 4.8.x or 5.x series. Exact fix versions should be confirmed via the Wireshark Foundation security advisory (https://www.wireshark.org/security/wnpa-sec-2026-47.html). If immediate patching is not feasible, implement the following mitigations: (1) restrict local access to sharkd via file system permissions and process isolation, limiting which users can invoke the service; (2) monitor sharkd process memory usage (RSS/VSZ) and implement automated restart policies when memory crosses defined thresholds, accepting brief service interruptions to prevent system-wide impact; (3) disable or restrict the sharkd service on systems where it is not actively required for operations; (4) if sharkd is exposed via network API, place it behind an authentication layer and rate-limit packet submission requests to slow memory exhaustion. Each mitigation carries trade-offs: memory-based auto-restart may mask the underlying issue and cause legitimate analysis interruptions, while service disablement may remove valuable packet analysis capabilities.