Skip to main content
Mallory
← Back to News
endpoint-software-vulnerabilitywidely-deployed-product-advisoryproof-of-concept-release

Wireshark BEEP Dissector Flaw Lets Malformed Packets Crash the Analyzer

Vulnerability Disclosure · 3 sources · Updated 3mo ago · First seen Apr 29, 2026

Wireshark BEEP Dissector Flaw Lets Malformed Packets Crash the Analyzer

Wireshark disclosed a denial-of-service vulnerability in its BEEP protocol dissector that can crash the packet analyzer through a stack-call overflow caused by recursive function handling. The issue is tracked as CVE-2026-6538 and documented in advisory wnpa-sec-2026-23, with the underlying bug reported in Wireshark's issue tracker as a BEEP dissector stack-call overflow.

The flaw affects Wireshark versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. According to the vendor, an attacker could trigger the crash by injecting a malformed packet onto the network or by convincing a user to open a crafted capture file. Wireshark said no active exploits are known, credited Sharon Brizinov with discovery, and released fixes in versions 4.6.5 and 4.4.15.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

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

2 events · Mar 30, 2026 – Apr 29, 2026
  1. Apr 29, 20267mo ago

    Wireshark publishes advisory WNPA-SEC-2026-23 for CVE-2026-6538

    Wireshark disclosed a BEEP dissector crash vulnerability, CVE-2026-6538, affecting versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. The advisory said malformed network packets or packet capture files could trigger a crash, credited Sharon Brizinov with discovery, noted no known exploits, and stated the issue was fixed in versions 4.6.5 and 4.4.15.

    Wireshark • Go Deep | Wireshark • wnpa-sec-2026-23 BEEP dissector crash
  2. Mar 30, 20268mo ago

    Wireshark issue 21120 opened for BEEP dissector stack-call overflow

    A GitLab issue was opened to track a stack-call overflow caused by a recursive function in Wireshark's BEEP dissector. This issue is referenced later by Wireshark's security advisory for CVE-2026-6538.

    Wireshark BEEP Dissector - Stack-call overflow caused by recursive function (#21120) · Issue · wireshark/wireshark
Linked entities

Related entities

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

Open in app →

Affected products

1 linked
Wireshark
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
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.