Medium [CVE-2026-96415] Stack-based Buffer Overflow in Wireshark
This medium-severity Red Hat Linux advisory covers CVE-2026-96415; 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
Stack-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
- Avoid processing packet capture files obtained from untrusted sources and avoid live packet capturing on untrusted networks. Alternatively, disable the Catapult DCT2000 protocol dissector if it is not required: 1. In the Wireshark GUI, open Analyze -> Enabled Protocols, search for "Catapult DCT2000" (or "dct2000"), uncheck the checkbox, and click OK. 2. For command-line analysis using TShark, supply the command-line flag: tshark --disable-protocol dct2000 Caveat: Disabling the dissector prevents Wireshark and TShark from decoding Catapult DCT2000 network traffic, rendering it as raw payload data.
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.