RF4CE protocol dissector denial of service in Wireshark
CVE-2026-96417 is a crash vulnerability in the Wireshark RF4CE protocol dissector affecting versions 4.6.0 through 4.6.8 and 4.4.0 through 4.4.18. An attacker can trigger a dissector crash, causing denial of service. The underlying programming defect and precise triggering input are not specified.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation crashes the RF4CE protocol dissector and disrupts the affected Wireshark application's availability. Arbitrary code execution is mentioned in advisories covering multiple Wireshark vulnerabilities, but is not established specifically for CVE-2026-96417.
If you can’t patch tonight, do this now.
Until updates are deployed, limit opening or processing untrusted packet captures and network traffic with affected Wireshark installations, and apply appropriate network and endpoint access controls. These are general exposure-reduction measures; no vulnerability-specific workaround is established.
Patch, then assume compromise.
Upgrade Wireshark 4.4.x to version 4.4.19 or later, or Wireshark 4.6.x to version 4.6.9 or later. On Debian 13 (trixie), upgrade the affected Wireshark packages to version 4.4.19-0+deb13u1 or later. These fixed releases supersede the earlier plugin notice describing the vulnerability as unpatched.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.