# CVE-2025-5601: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') in Wireshark

> Attackers can cause Wireshark to crash via crafted packets or capture files, leading to denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 4 Jun 2025
- **Updated:** 27 Mar 2026
- **Also known as:** DEBIAN-CVE-2025-5601, GHSA-fqw2-jpxp-qh8x, SUSE-SU-2025:01968-1, SUSE-SU-2025:02271-1, SUSE-SU-2025:02272-1, UBUNTU-CVE-2025-5601, openSUSE-SU-2025:15308-1

## What is CVE-2025-5601?

CVE-2025-5601 is a high-severity memory corruption vulnerability in Wireshark Wireshark, published on 4 Jun 2025. 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

Column handling crashes in Wireshark 4.4.0 to 4.4.6 and 4.2.0 to 4.2.12 allows denial of service via packet injection or crafted capture file

Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-5601?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wireshark` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 4.2.12-150600.18.23.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 3.6.24-150000.3.121.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 4.2.12-150600.18.23.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | All versions | 4.2.12-150600.18.23.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP7 | All versions | 4.2.12-150600.18.23.1 |
| `wireshark` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.4.16-48.63.1 |
| `wireshark` | openSUSE:Leap 15.6 | All versions | 4.2.12-150600.18.23.1 |
| `wireshark` | openSUSE:Tumbleweed | All versions | 4.4.7-1.1 |

Products: Wireshark Wireshark.

## How do I fix CVE-2025-5601?

Upgrade to a fixed version.

## Is CVE-2025-5601 being exploited?

There is no known exploitation of CVE-2025-5601 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-2025-5601 and fix it if it is affected.

What it is: CVE-2025-5601 is a high-severity memory corruption vulnerability in Wireshark Wireshark, published on 4 Jun 2025. 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-2025-5601 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-2025-5601/ (Markdown: https://insights.sbomify.com/CVE-2025-5601/index.md)
```

## Sources

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

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