Analyzer hang via MEGACO dissector loop
Published Dec 3, 2025 · Updated Mar 27, 2026
Infinite looping in the MEGACO dissector in Wireshark 4.4.0 through 4.4.11 and 4.6.0 through 4.6.1 allows attackers to cause a hang. The vendor has not published which MEGACO parsing loop fails to advance or terminate on malformed input. The packet must be injected onto a monitored network or opened as a capture file; successful processing consumes excessive CPU and hangs the analyzer.
Summary
What happened
Infinite looping in the MEGACO dissector in Wireshark 4.4.0 through 4.4.11 and 4.6.0 through 4.6.1 allows attackers to cause a hang. The vendor has not published which MEGACO parsing loop fails to advance or terminate on malformed input. The packet must be injected onto a monitored network or opened as a capture file; successful processing consumes excessive CPU and hangs the analyzer.
The record
- CVE
- CVE-2025-13946
- Published
- Dec 3, 2025
- Updated
- Mar 27, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-835, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 3, 2025CVE publishedPublication date reported by the CVE source.
- Mar 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.4.0 <4.4.11
- Affected versionversion=4.6.0 <4.6.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo