Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-15167: Heap buffer overflow in Wireshark DBS Etherwatch file parser

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.27%20th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-15167CWE-122

CVE-2026-15167 is a heap-based buffer overflow in Wireshark's DBS Etherwatch capture-file reader affecting versions 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16. When parsing a packet's textual hexadecimal dump, the reader writes decoded bytes into a heap-allocated record buffer without checking bounds for each write. Its length guard runs only after an entire dump line has been written, allowing a crafted line to write attacker-controlled bytes beyond the allocation. Opening or automatically processing a malicious capture file can trigger memory corruption and crash the application. The vulnerability was fixed in Wireshark 4.6.7 and 4.4.17.

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 can crash Wireshark or an application using the vulnerable libwiretap reader, causing denial of service and interrupting capture-analysis workflows. The attacker controls the contents and length of the out-of-bounds heap write. Although this constitutes a memory-corruption primitive, arbitrary code execution and confidentiality or integrity compromise have not been established for this CVE.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid opening untrusted DBS Etherwatch capture files and suspend their automatic ingestion into capture-processing services. Restrict submission access to analysis workflows and run unavoidable parsing in isolated, least-privileged environments. Filename or extension filtering alone is insufficient because the reader detects the format from file contents.

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. For distribution-managed installations, install the vendor's fixed packages, including applicable Wireshark libraries and command-line tools. Fixed distribution packages include Debian 13 version 4.4.18-0+deb13u1, Fedora 43 version 4.6.8-1.fc43, Fedora 44 version 4.6.8-1.fc44, and Alpine version 4.6.9-r0. SUSE users should install the applicable backported security update. The upstream code correction ensures the record buffer has sufficient slack for an additional dump line.

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-15167 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-15167 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-15167?
Yes. As of Nov 6, 2026, Mallory has reports of a public exploit for CVE-2026-15167.
Is there a patch for CVE-2026-15167?
Upgrade to Wireshark 4.6.7 or later in the 4.6 branch, or 4.4.17 or later in the 4.4 branch. For distribution-managed installations, install the vendor's fixed packages, including applicable Wireshark libraries and command-line tools.
What products are affected by CVE-2026-15167?
Wireshark Foundation Wireshark.
How severe is CVE-2026-15167?
CVE-2026-15167 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.27% (20th percentile) as of Nov 6, 2026.
Activity feed

Recent activity

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

View more in app →
+14 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.