# CVE-2026-3201: Improperly Controlled Sequential Memory Allocation in Wireshark

> Attackers can cause denial of service in Wireshark via memory exhaustion in the USB HID protocol dissector.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Feb 2026
- **Updated:** 27 Mar 2026
- **Also known as:** AZL-78336, DEBIAN-CVE-2026-3201, GHSA-3g96-v3mg-9xp9, SUSE-SU-2026:0810-1, UBUNTU-CVE-2026-3201

## What is CVE-2026-3201?

CVE-2026-3201 is a medium-severity denial of service vulnerability in Wireshark Wireshark, published on 25 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-1325 (Improperly Controlled Sequential Memory Allocation)

## Which versions are affected by CVE-2026-3201?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wireshark` | openSUSE:Leap 15.6 | All versions | 4.2.14-150600.18.38.1 |

Products: Wireshark Wireshark.

## How do I fix CVE-2026-3201?

Upgrade to a fixed version.

## Is CVE-2026-3201 being exploited?

There is no known exploitation of CVE-2026-3201 in the wild and no public exploit code.

## Other vulnerabilities in Wireshark Wireshark

- [CVE-2011-0444](https://insights.sbomify.com/CVE-2011-0444/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2994](https://insights.sbomify.com/CVE-2010-2994/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2995](https://insights.sbomify.com/CVE-2010-2995/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1266](https://insights.sbomify.com/CVE-2009-1266/): Other in n/a (critical 10.0)
- [CVE-2009-1210](https://insights.sbomify.com/CVE-2009-1210/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3201 and fix it if it is affected.

What it is: CVE-2026-3201 is a medium-severity denial of service vulnerability in Wireshark Wireshark, published on 25 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-3201 in the wild and no public exploit code.

Affected product: Wireshark Wireshark. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3201/ (Markdown: https://insights.sbomify.com/CVE-2026-3201/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3201
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3201
- OSV: https://osv.dev/vulnerability/CVE-2026-3201

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3201/
Summaries are generated and may contain mistakes; the official description above is the record.