# CVE-2026-15166: Stack-based Buffer Overflow in Wireshark


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** AZL-92138, DEBIAN-CVE-2026-15166, GHSA-h9wc-3j4p-q5g3, MINI-8423-mfrx-v8ff, UBUNTU-CVE-2026-15166

## What is CVE-2026-15166?

CVE-2026-15166 is a medium-severity vulnerability in Wireshark Wireshark, published on 8 Jul 2026. 

### Official description

IEEE 802.11 protocol dissector crash in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows denial of service

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Wireshark Wireshark.

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

Upgrade to a fixed version.

## Is CVE-2026-15166 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15166 exists.

## 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-15166 and fix it if it is affected.

What it is: CVE-2026-15166 is a medium-severity vulnerability in Wireshark Wireshark, published on 8 Jul 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15166 exists.

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-15166/ (Markdown: https://insights.sbomify.com/CVE-2026-15166/index.md)
```

## Sources

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

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