Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-15174: Out-of-bounds write in Wireshark Catapult DCT2000 dissector

Published Jul 8, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 1 in a dayToday
CVSS5.5Medium · v3.1
EPSS0.13%3rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-15174CWE-787

CVE-2026-15174 is an out-of-bounds write vulnerability in the Catapult DCT2000 protocol dissector in Wireshark 4.6.0–4.6.6 and 4.4.0–4.4.16. The E-DCH parsing branch of attach_fp_info() accepts the capture-header field no_ddi_entries without bounding it. This value controls writes into the fixed-size edch_ddi and edch_macd_pdu_size arrays in struct fp_info. An oversized count causes writes beyond those arrays, corrupting Wireshark's wmem allocator metadata and triggering a subsequent segmentation fault. Crafted capture input can therefore crash Wireshark and cause denial of service. This flaw is distinct from the Catapult DCT2000 file-reader off-by-one vulnerability CVE-2026-76883.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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 crashes the affected Wireshark process, interrupting packet analysis and causing application-level denial of service. Allocator-state corruption and crashes were demonstrated both with sanitizers and on a stock glibc build. Arbitrary code execution, confidentiality loss, 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 capture files and limit analysis of attacker-controlled traffic. These precautions reduce exposure to the documented input paths but do not correct the underlying bounds-checking flaw.

Remediation

Patch, then assume compromise.

Upgrade to Wireshark 4.6.7 or later in the 4.6 branch, or 4.4.17 or later in the 4.4 branch. The fix bounds no_ddi_entries to MAX_EDCH_DDIS immediately after reading the header value, preventing writes beyond the fixed-size arrays. For distribution-managed installations, apply the vendor's corrected Wireshark packages; Debian 13 provides fixes in 4.4.18-0+deb13u1.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
Wireshark FoundationWiresharkapplication
FAQ

Frequently asked questions

Is CVE-2026-15174 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-15174 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-15174?
Yes. As of Nov 6, 2026, Mallory has reports of a public exploit for CVE-2026-15174.
Is there a patch for CVE-2026-15174?
Upgrade to Wireshark 4.6.7 or later in the 4.6 branch, or 4.4.17 or later in the 4.4 branch. The fix bounds no_ddi_entries to MAX_EDCH_DDIS immediately after reading the header value, preventing writes beyond the fixed-size arrays.
What products are affected by CVE-2026-15174?
Wireshark Foundation Wireshark.
How severe is CVE-2026-15174?
CVE-2026-15174 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.13% (3rd percentile) as of Nov 6, 2026.
Activity feed

Recent activity

23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.