CVE-2017-11406: In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the DOCSIS dissector could go into an infinite loop.

Security readout for executives and security teams

Wireshark versions in the listed 2.2.x and 2.0.x ranges could hang while analyzing certain DOCSIS data. For most organizations, the main risk is analyst workstation or automated packet-processing disruption, not system takeover. No provided source shows active exploitation. Exposure is likely limited to systems running the affected Wireshark versions and analyzing DOCSIS packet data or captures. Security analysts, network operations teams, and automated capture-processing workflows are the most relevant targets. Treat as a targeted reliability issue for network analysis tooling. Prioritize remediation where Wireshark is used in SOC, network operations, or automated capture pipelines, especially if analysts handle untrusted packet captures. Mitigation focus: Inventory Wireshark installations and identify affected 2.2.x or 2.0.x versions.; Upgrade Wireshark using vendor or distribution security guidance.; Apply the Debian LTS Wireshark update where Debian packages are used..

Prepared

Jun 13, 2026, 04:25 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.