Skip to main content
Mallory
← Back to News
widely-deployed-product-advisoryendpoint-software-vulnerabilityproof-of-concept-release

Wireshark Fixes Catapult DCT2000 Parser Flaws Causing Crash and Heap Overflow

Patch & Detection Intelligence · 3 sources · Updated 3mo ago · First seen Aug 21, 2026

Wireshark Fixes Catapult DCT2000 Parser Flaws Causing Crash and Heap Overflow

Wireshark disclosed and patched multiple vulnerabilities in its Catapult DCT2000 handling code, including a protocol dissector crash tracked as CVE-2026-15174 and a separate file parser flaw later assigned CVE-2026-76883. The first issue, published as advisory wnpa-sec-2026-52, affects Wireshark versions 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16 and can be triggered by a malformed packet on the wire or by opening a malformed packet trace file, causing the application to crash.

A later advisory, wnpa-sec-2026-74, covers a Catapult DCT2000 file parser crash affecting versions 4.6.0 through 4.6.7 and 4.4.0 through 4.4.17, fixed in 4.6.8 and 4.4.18. Separately, a GitLab issue detailed an off-by-one heap out-of-bounds write in parse_line() within wiretap/catapult_dct2000.c, where the parser allocates floor(data_chars/2) bytes but may write ceil(data_chars/2) bytes when the input length is odd; developers confirmed the bug, noted practical triggering requires exactly 2049 bytes, and merged fixes. Wireshark said no exploits are known for the disclosed issues and advised users to upgrade to patched releases.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Jul 8, 2026 – Aug 12, 2026
  1. Aug 12, 20263mo ago

    Wireshark publishes wnpa-sec-2026-74 for Catapult DCT2000 file parser crash

    On August 12, 2026, Wireshark published security notice wnpa-sec-2026-74 for a Catapult DCT2000 file parser crash affecting versions 4.6.0 through 4.6.7 and 4.4.0 through 4.4.17. The notice credits Yazan Balawneh of the CyStack Security Team, references issue 21427, and says the flaw was fixed in versions 4.6.8 and 4.4.18.

    Wireshark • Go Deep | Wireshark • wnpa-sec-2026-74 Catapult DCT2000 file parser crash
  2. Reported Jul 21, 20264mo ago

    Wireshark fixes issue 21427 and later assigns CVE-2026-76883

    Wireshark developers confirmed and fixed the Catapult DCT2000 file reader bug through merged merge requests tied to issue 21427, and Gerald Combs later stated the vulnerability had been assigned CVE-2026-76883. The issue record says it was initially handled as a security issue before being made publicly visible.

    Heap OOB write in wiretap/catapult_dct2000.c:1382 - off-by-one in DCT2000 file reader (#21427) · Issue · wireshark/wireshark
  3. Jul 21, 20264mo ago

    CyStack reports separate Catapult DCT2000 file reader overflow

    A GitLab issue created on July 21, 2026 reported a distinct heap out-of-bounds write in Wireshark's Catapult DCT2000 wiretap file reader, caused by an off-by-one allocation bug in parse_line(). The report, submitted by Yazan Balawneh of the CyStack Security Team, noted the flaw was separate from wnpa-sec-2026-52 / CVE-2026-15174 and included a proof-of-concept malformed file.

    Heap OOB write in wiretap/catapult_dct2000.c:1382 - off-by-one in DCT2000 file reader (#21427) · Issue · wireshark/wireshark
  4. Jul 8, 20264mo ago

    Wireshark publishes advisory wnpa-sec-2026-52 for CVE-2026-15174

    On July 8, 2026, Wireshark disclosed security advisory wnpa-sec-2026-52 for a Catapult DCT2000 protocol dissector crash tracked as CVE-2026-15174. The issue affects versions 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16, and Wireshark said it was fixed in 4.6.7 and 4.4.17.

    Wireshark • Go Deep | Wireshark • wnpa-sec-2026-52 Catapult DCT2000 protocol dissector crash
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.