CVE-2026-3201: CWE-1325: Improperly Controlled Sequential Memory Allocation in Wireshark Foundation Wireshark
USB HID protocol dissector memory exhaustion in Wireshark 4.6.0 to 4.6.3 and 4.4.0 to 4.4.13 allows denial of service
AI Analysis
Technical Summary
CVE-2026-3201 is a vulnerability identified in the Wireshark network protocol analyzer, specifically affecting versions 4.4.0 through 4.4.13 and 4.6.0 through 4.6.3. The flaw resides in the USB Human Interface Device (HID) protocol dissector, where sequential memory allocation is improperly controlled. This improper handling can lead to memory exhaustion when processing crafted USB HID traffic or capture files, causing the application to crash or become unresponsive, effectively resulting in a denial of service (DoS). The vulnerability is classified under CWE-1325, which involves improper control of sequential memory allocation, a condition that can be exploited to exhaust system resources. According to the CVSS v3.1 score of 4.7, the attack vector is local (AV:L), requiring high attack complexity (AC:H), no privileges (PR:N), and user interaction (UI:R). The scope remains unchanged (S:U), and the impact is limited to availability (A:H) without affecting confidentiality or integrity. No known exploits have been reported in the wild, and no official patches have been linked at the time of publication. The vulnerability highlights the risk of processing untrusted or malformed USB HID capture data within Wireshark, which is widely used for network troubleshooting and security analysis.
Potential Impact
The primary impact of CVE-2026-3201 is a denial of service condition affecting Wireshark users who analyze USB HID traffic. This can disrupt network analysis workflows, delay incident response, and potentially cause loss of volatile forensic data if Wireshark crashes during capture or analysis. Organizations relying on Wireshark for monitoring USB device communications, especially in environments where USB HID devices are prevalent, may experience operational interruptions. While the vulnerability does not allow for data leakage or code execution, the availability impact can hinder security teams and network administrators. In critical infrastructure sectors or environments with stringent monitoring requirements, repeated exploitation could degrade the reliability of network diagnostics. Since exploitation requires local access and user interaction, remote attacks are unlikely, limiting the threat scope primarily to internal or physically proximate attackers.
Mitigation Recommendations
To mitigate CVE-2026-3201, organizations should: 1) Avoid opening or analyzing untrusted or suspicious USB HID capture files in affected Wireshark versions. 2) Implement strict access controls to limit who can run Wireshark and analyze USB HID traffic, reducing the risk of local exploitation. 3) Monitor Wireshark Foundation announcements closely for patches or updates addressing this vulnerability and apply them promptly once available. 4) Use alternative tools or versions not affected by this vulnerability when analyzing USB HID traffic if immediate patching is not possible. 5) Employ endpoint security measures to detect and prevent attempts to exploit local vulnerabilities, including monitoring for abnormal Wireshark crashes or resource exhaustion events. 6) Educate users about the risks of opening untrusted capture files and enforce policies to prevent such actions. These steps go beyond generic advice by focusing on controlling the attack vector (USB HID capture files) and limiting local exploitation opportunities.
Affected Countries
United States, Germany, United Kingdom, France, Japan, South Korea, Canada, Australia, Netherlands, Sweden
CVE-2026-3201: CWE-1325: Improperly Controlled Sequential Memory Allocation in Wireshark Foundation Wireshark
Description
USB HID protocol dissector memory exhaustion in Wireshark 4.6.0 to 4.6.3 and 4.4.0 to 4.4.13 allows denial of service
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-3201 is a vulnerability identified in the Wireshark network protocol analyzer, specifically affecting versions 4.4.0 through 4.4.13 and 4.6.0 through 4.6.3. The flaw resides in the USB Human Interface Device (HID) protocol dissector, where sequential memory allocation is improperly controlled. This improper handling can lead to memory exhaustion when processing crafted USB HID traffic or capture files, causing the application to crash or become unresponsive, effectively resulting in a denial of service (DoS). The vulnerability is classified under CWE-1325, which involves improper control of sequential memory allocation, a condition that can be exploited to exhaust system resources. According to the CVSS v3.1 score of 4.7, the attack vector is local (AV:L), requiring high attack complexity (AC:H), no privileges (PR:N), and user interaction (UI:R). The scope remains unchanged (S:U), and the impact is limited to availability (A:H) without affecting confidentiality or integrity. No known exploits have been reported in the wild, and no official patches have been linked at the time of publication. The vulnerability highlights the risk of processing untrusted or malformed USB HID capture data within Wireshark, which is widely used for network troubleshooting and security analysis.
Potential Impact
The primary impact of CVE-2026-3201 is a denial of service condition affecting Wireshark users who analyze USB HID traffic. This can disrupt network analysis workflows, delay incident response, and potentially cause loss of volatile forensic data if Wireshark crashes during capture or analysis. Organizations relying on Wireshark for monitoring USB device communications, especially in environments where USB HID devices are prevalent, may experience operational interruptions. While the vulnerability does not allow for data leakage or code execution, the availability impact can hinder security teams and network administrators. In critical infrastructure sectors or environments with stringent monitoring requirements, repeated exploitation could degrade the reliability of network diagnostics. Since exploitation requires local access and user interaction, remote attacks are unlikely, limiting the threat scope primarily to internal or physically proximate attackers.
Mitigation Recommendations
To mitigate CVE-2026-3201, organizations should: 1) Avoid opening or analyzing untrusted or suspicious USB HID capture files in affected Wireshark versions. 2) Implement strict access controls to limit who can run Wireshark and analyze USB HID traffic, reducing the risk of local exploitation. 3) Monitor Wireshark Foundation announcements closely for patches or updates addressing this vulnerability and apply them promptly once available. 4) Use alternative tools or versions not affected by this vulnerability when analyzing USB HID traffic if immediate patching is not possible. 5) Employ endpoint security measures to detect and prevent attempts to exploit local vulnerabilities, including monitoring for abnormal Wireshark crashes or resource exhaustion events. 6) Educate users about the risks of opening untrusted capture files and enforce policies to prevent such actions. These steps go beyond generic advice by focusing on controlling the attack vector (USB HID capture files) and limiting local exploitation opportunities.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitLab
- Date Reserved
- 2026-02-25T14:35:36.231Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f0a1db7ef31ef0b25eb19
Added to database: 2/25/2026, 2:41:33 PM
Last enriched: 3/27/2026, 6:23:19 PM
Last updated: 4/12/2026, 9:10:51 AM
Views: 159
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.