Medium [CVE-2026-96423] Heap-based Buffer Overflow in Wireshark
This medium-severity Red Hat Linux advisory covers CVE-2026-96423; related products: Red Hat Enterprise Linux 10, Red Hat package: wireshark.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Heap-based Buffer Overflow in Wireshark. Red Hat rates this moderate (CVSS 5.5).
Weakness: CWE-787.
Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat package: wireshark.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Mitigation checklist
- Disable the X11 protocol dissector if analyzing network traffic that does not require X11 packet decoding. For command-line analysis using tshark, disable the protocol at runtime: ``` tshark --disable-protocol x11 -r <capture_file> ``` For persistent user configuration, add the protocol identifier to the disabled protocols file: ``` mkdir -p ~/.config/wireshark echo "x11" >> ~/.config/wireshark/disabled_protos ``` In the Wireshark graphical interface, the dissector can be disabled by navigating to Analyze > Enabled Protocols, searching for "X11", unchecking the protocol entry, and clicking OK. Caveats: Disabling this dissector prevents Wireshark from decoding and analyzing X11 protocol traffic. Running Wireshark sessions must be restarted for configuration file changes to take effect. Additionally, avoid opening capture files obtained from untrusted sources and avoid running packet capture utilities with elevated root privileges.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.