CVE-2026-76883: Heap Buffer Overflow in Wireshark Catapult DCT2000 File Reader
- Vendor
- Wireshark Foundation
CVE-2026-76883 is a heap-based buffer overflow in parse_line() in Wireshark's Catapult DCT2000 wiretap file reader. The parser calculates the required allocation as floor(data_chars/2), but writes ceil(data_chars/2) bytes when data_chars is odd, potentially producing a one-byte out-of-bounds write. Existing buffer allocation behavior restricts practical triggering to a specific 2049-byte boundary condition involving an initially allocated 2048-byte buffer. Opening a specially crafted DCT2000 capture in Wireshark or TShark can trigger the overflow and crash the application. Affected release ranges are identified as 4.6.0 through 4.6.7 and 4.4.0 through 4.4.18; distribution packages may incorporate backported fixes.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can crash Wireshark, TShark, or another application using the affected file reader, interrupting capture analysis and causing denial of service. The demonstrated memory corruption is a one-byte heap out-of-bounds write. Arbitrary code execution, information disclosure, and integrity compromise have not been established for this CVE.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid opening untrusted Catapult DCT2000 captures with affected Wireshark or TShark installations. Prevent untrusted DCT2000 inputs from reaching automated capture-analysis workflows. If analysis is necessary, use an isolated, disposable environment to limit the consequences of a parser crash; isolation does not correct the vulnerability.
Remediation
Patch, then assume compromise.
Install a vendor-patched Wireshark release or distribution security update explicitly addressing CVE-2026-76883. For Debian 13 (trixie), the identified fixed package version is 4.4.18-0+deb13u1. For Amazon Linux 2023, apply ALAS2023-2026-2117. Do not determine patch status solely from the upstream version number because distribution fixes may be backported. For source-maintained builds, incorporate the upstream fix; the allocation mismatch can be corrected by allocating (data_chars + 1) / 2 bytes or rejecting odd-length encoded data before conversion.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-76883 exploited in the wild?
- As of Nov 4, 2026, Mallory has no reports of CVE-2026-76883 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-76883?
- Yes. As of Nov 4, 2026, Mallory has reports of a public exploit for CVE-2026-76883.
- Is there a patch for CVE-2026-76883?
- Install a vendor-patched Wireshark release or distribution security update explicitly addressing CVE-2026-76883. For Debian 13 (trixie), the identified fixed package version is 4.4.18-0+deb13u1.
- What products are affected by CVE-2026-76883?
- Wireshark Foundation Wireshark.
- How severe is CVE-2026-76883?
- CVE-2026-76883 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.13% (3rd percentile) as of Nov 4, 2026.
Recent activity
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.