dbcve.org
WiresharkApplication

CVE-2026-15174

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 4.4.17 / 4.6.7 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Catapult DCT2000 protocol dissector crash in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows denial of service

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Catapult DCT2000 protocol dissector in Wireshark contains a crash vulnerability affecting versions 4.6.0-4.6.6 and 4.4.0-4.4.16. By processing a malformed packet in the DCT2000 protocol, an attacker can trigger Wireshark to crash, causing denial of service.

MitigationUpdate Wireshark to version 4.6.7 or later (or 4.4.17 or later) to obtain the patch. Alternatively, avoid opening untrusted packet capture files or limit processing of Catapult DCT2000 traffic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WiresharkApplication
Affected:>= 4.4.0, < 4.4.17>= 4.6.0, < 4.6.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Wireshark version
    Run 'wireshark --version' or 'tshark --version' to identify the exact version number installed
    Affected if version is 4.4.0 through 4.4.16, or 4.6.0 through 4.6.6 (vulnerable range)
  2. Verify DCT2000 protocol dissector is present
    Check Wireshark installation for the DCT2000 dissector module (commonly in plugins or epan directories under names like dct2000 or similar)
    Affected if the Catapult DCT2000 dissector file exists in the Wireshark installation directory
  3. Confirm protocol support is enabled
    Launch Wireshark, go to Help > About > Plugins or examine the enabled protocol list for DCT2000-related entries
    Affected if the DCT2000 or Catapult protocol dissector appears in the enabled dissectors list
  4. Check for recent crash activity related to DCT2000
    Review any existing crash logs or core dumps for patterns mentioning 'DCT2000' or 'Catapult' in the stack trace
    Affected if crash logs show DCT2000 dissector involvement when processing capture files

User is affected if Wireshark version falls within 4.4.0-4.4.16 or 4.6.0-4.6.6 AND the Catapult DCT2000 protocol dissector is present and enabled in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.4.17 / 4.6.7 or later
Fixed in 4.4.174.6.7
Interim mitigation

Update Wireshark to version 4.6.7 or later (or 4.4.17 or later) to obtain the patch. Alternatively, avoid opening untrusted packet capture files or limit processing of Catapult DCT2000 traffic.

Recommended fix High confidence

Wireshark 4.4.17 or 4.6.7 (latest available in your branch)

  1. 1. Identify the currently installed Wireshark version using 'wireshark --version' or 'tshark --version'
  2. 2. If running version 4.4.0 through 4.4.16, upgrade to version 4.4.17 or later
  3. 3. If running version 4.6.0 through 4.6.6, upgrade to version 4.6.7 or later
  4. 4. For package managers (apt, yum, brew, etc.), update using the standard package update process
  5. 5. Verify the upgrade was successful by checking 'wireshark --version' shows a fixed version
  6. 6. If using Wireshark capture files as input, re-parse any previously captured files to ensure they are processed by the fixed dissector
Caveat Minor version upgrades within the same major release typically have no breaking changes; however, always review release notes for changes to protocol dissectors you use

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wireshark Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15174 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data