Red Hat Security Advisory: wireshark security update
🔗 CVE IDs covered (1)
📋 Description
CVE-2026-95387 — wireshark: wireshark: Denial of Service via heap-based buffer overflow in SPDY dissector
🎯 Affected products47
- Red Hat Enterprise Linux AppStream (v. 8)
- Red Hat Enterprise Linux CRB (v. 8)
- wireshark-1:2.6.2-22.el8_10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-1:2.6.2-22.el8_10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-1:2.6.2-22.el8_10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-1:2.6.2-22.el8_10.src as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-1:2.6.2-22.el8_10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-1:2.6.2-22.el8_10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-1:2.6.2-22.el8_10.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-1:2.6.2-22.el8_10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-1:2.6.2-22.el8_10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-1:2.6.2-22.el8_10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.aarch64 as a component of Red Hat Enterprise Linux CRB (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.i686 as a component of Red Hat Enterprise Linux CRB (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.ppc64le as a component of Red Hat Enterprise Linux CRB (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.s390x as a component of Red Hat Enterprise Linux CRB (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-cli-debuginfo-1:2.6.2-22.el8_10.x86_64 as a component of Red Hat Enterprise Linux CRB (v. 8)
- wireshark-debuginfo-1:2.6.2-22.el8_10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-debuginfo-1:2.6.2-22.el8_10.aarch64 as a component of Red Hat Enterprise Linux CRB (v. 8)
- wireshark-debuginfo-1:2.6.2-22.el8_10.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-debuginfo-1:2.6.2-22.el8_10.i686 as a component of Red Hat Enterprise Linux CRB (v. 8)
- wireshark-debuginfo-1:2.6.2-22.el8_10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-debuginfo-1:2.6.2-22.el8_10.ppc64le as a component of Red Hat Enterprise Linux CRB (v. 8)
- wireshark-debuginfo-1:2.6.2-22.el8_10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
- wireshark-debuginfo-1:2.6.2-22.el8_10.s390x as a component of Red Hat Enterprise Linux CRB (v. 8)
- +17 more not shown
✅ Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Disable the SPDY protocol dissector in Wireshark or TShark to prevent processing of the vulnerable protocol format. For TShark command-line usage, pass the protocol disable flag: ``` tshark --disable-protocol spdy -r <capture_file> ``` For persistent configuration across sessions, append the protocol to the disabled protocols file: ``` echo "spdy" >> ~/.config/wireshark/disabled_protos ``` In the Wireshark graphical interface: 1. Navigate to Analyze -> Enabled Protocols... 2. Search for "SPDY" and clear the checkbox. 3. Click OK or Save. Caveat: Disabling the dissector prevents the decoding and inspection of SPDY protocol streams, treating them as generic TCP or TLS payload. Wireshark must be restarted if it is currently running for configuration changes to take effect. Always ensure capture analysis is conducted with non-privileged user privileges.