Loading story…
Wireshark disclosed CVE-2026-6524, a flaw in its MySQL protocol dissector that can crash the application when it parses a malformed packet or packet capture. The bug was traced to a commented-out initialization of the param_metas->encodings pointer, which was later dereferenced in mysql_dissect_request in packet-mysql.c, causing a segmentation fault. A proof-of-concept packet capture reportedly reproduced the crash in Wireshark/TShark 4.7.0 on Linux, with AddressSanitizer output confirming the fault.
The vendor said the issue affects Wireshark versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. An attacker could trigger the denial-of-service condition by injecting a malformed packet onto the network or by convincing a user to open a crafted capture file. Wireshark said it has no evidence of exploitation in the wild and released fixes in 4.6.5 and 4.4.15; the issue was credited to Alexandre de Oliveira and linked to upstream fixes for MySQL bulk execute statement parameter handling.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
The CVE record for CVE-2026-6524 was published, describing a denial-of-service flaw in Wireshark's MySQL protocol dissector caused by access of an uninitialized pointer. The record lists affected versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14, fixed versions 4.6.5 and 4.4.15, and credits Alexandre de Oliveira.
Wireshark published security advisory wnpa-sec-2026-37 disclosing a MySQL protocol dissector crash tracked as CVE-2026-6524. The advisory said versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14 were affected, and that fixes were released in versions 4.6.5 and 4.4.15.
A GitLab issue was created for a Wireshark MySQL dissector bug in which a commented-out pointer initialization could be dereferenced, causing a crash when a crafted packet capture was opened or parsed. The report included a proof-of-concept pcap and reproduction details showing a denial-of-service condition during packet dissection.
The reported MySQL dissector crash was assigned CVE-2026-6524, and the upstream issue was later closed as done after remediation. The issue references merged fixes related to MySQL bulk execute statement parameter handling, and the closure is attributed to Anders Broman with commit 62a4c4ba.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cve.mitre.org
Open sourcewireshark.org
Open sourcegitlab.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Wireshark disclosed **CVE-2026-5653**, a heap-based buffer overflow in its DCP-ETSI protocol dissector that can crash the network protocol analyzer and cause a denial of service. The flaw affects Wireshark versions `4.6.0` through `4.6.4` and `4.4.0` through `4.4.14`, and was assigned **CWE-122** with a **CVSS v3.1 score of 5.5**. According to the advisory, an attacker could trigger the issue by injecting a malformed packet onto the network or by convincing a user to open a crafted packet capture file. Wireshark fixed the vulnerability in versions `4.6.5` and `4.4.15`; the issue was discovered by Alexandre de Oliveira, and the vendor said no active exploits were known at the time of disclosure.
Aug 21, 2026
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**.
Aug 21, 2026
Wireshark disclosed **CVE-2026-6532**, a crash-causing flaw in the **Kismet protocol dissector** that can be triggered by a malformed packet on the network or by opening a crafted packet capture file. The issue affects Wireshark versions **4.6.0 through 4.6.4** and **4.4.0 through 4.4.14**, and has been fixed in **4.6.5** and **4.4.15**. Wireshark said no exploits are known and credited **Sharon Brizinov** with discovering the vulnerability. A related fuzzing report showed a **heap-buffer-overflow** in `tshark` while processing a crafted capture, with the crash occurring in `format_text_internal` and being reached through `packet-kismet.c` during packet dissection. The bug was reproduced in Wireshark's CI fuzzing environment on Ubuntu 24.04.4 LTS, and the original crash report was later marked as a duplicate of a dedicated Kismet dissector issue and explicitly assigned **CVE-2026-6532**.
Aug 21, 2026