PatchSiren cyber security CVE debrief
CVE-2026-6519 Wireshark Foundation CVE debrief
A vulnerability in the MBIM protocol dissector in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows for denial of service. This CVE was published on 2026-04-30T07:16:39.030Z and was last modified on 2026-10-26T00:10:00.150Z. The vulnerability is caused by an infinite loop in the MBIM protocol dissector, which can be exploited to cause a denial of service. Network administrators and security teams should assess exposure and apply patches or mitigations. The CVE record and NVD vulnerability detail page provide information on the vulnerability, including its CVSS score and affected versions.
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-30
- Original CVE updated
- 2026-10-26
- Advisory published
- 2026-04-30
- Advisory updated
- 2026-10-26
Who should care
Network administrators and security teams responsible for managing Wireshark installations should assess exposure and apply patches or mitigations. They should review network configurations and Wireshark versions to determine if they are affected by the vulnerability. Additionally, they should monitor network traffic for potential exploitation attempts and apply patches or updates to affected versions.
Why it matters
CVE-2026-6519 is a medium-severity vulnerability in Wireshark that allows for denial of service. Network administrators and security teams should assess exposure and apply patches or mitigations.
- Denial of service attacks may be launched against vulnerable Wireshark installations
- Network administrators must assess exposure and apply patches or mitigations
- Security teams should monitor network traffic for potential exploitation attempts
Technical summary
The MBIM protocol dissector in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 is vulnerable to an infinite loop, allowing for denial of service. The vulnerability is caused by a flaw in the MBIM protocol dissector that allows an attacker to cause an infinite loop, resulting in a denial of service. Network administrators and security teams should assess exposure and apply patches or mitigations.
Defensive priority
Medium priority for network administrators and security teams to assess exposure and apply patches or mitigations.
Recommended defensive actions
- Assess exposure by reviewing network configurations and Wireshark versions
- Apply patches or updates to affected versions
- Monitor network traffic for potential exploitation attempts
Evidence notes
The CVE record and NVD vulnerability detail page provide information on the vulnerability, including its CVSS score and affected versions. The vulnerability is caused by an infinite loop in the MBIM protocol dissector, which can be exploited to cause a denial of service. Network administrators and security teams should assess exposure and apply patches or mitigations. The evidence is limited to the information provided in the CVE record and NVD vulnerability detail page.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-6519 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-6519
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-6519 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-6519
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://gitlab.com/wireshark/wireshark/-/work_items/21184
[email protected] - Exploit, Issue Tracking, Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://www.wireshark.org/security/wnpa-sec-2026-41.html
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.