CVE-2016-9376: In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the OpenFlow dissector could crash with memory exhaustion,...

Security readout for executives and security teams

This flaw can make Wireshark crash from memory exhaustion when it processes certain OpenFlow traffic or a capture file. The business impact is disruption of packet-analysis work, not evidence of system takeover. Exposure is mainly security, network, and support teams using affected Wireshark versions. Organizations are exposed if analysts, jump boxes, lab systems, or automated packet-processing workflows use the affected Wireshark versions and inspect OpenFlow traffic or untrusted capture files. Prioritize remediation for security operations and network engineering systems that process external or untrusted captures. This is not described as code execution, but it can interrupt investigations and monitoring workflows. Mitigation focus: Upgrade Wireshark to a vendor-supported release outside the affected version ranges.; Apply Debian or other distribution security updates where Wireshark is packaged by the operating system.; Avoid opening untrusted capture files on vulnerable Wireshark installations..

Prepared

Jun 13, 2026, 13:16 UTC (UTC+00:00)

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