# CVE-2025-54351: Memory corruption in iperf3

> A buffer overflow in iperf3 allows attackers to execute code or cause denial of service when the skip-rx-copy option is enabled.

- **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Aug 2025
- **Updated:** 4 Aug 2025
- **Also known as:** ALPINE-CVE-2025-54351, BELL-CVE-2025-54351, GHSA-xjwm-4pfw-49g2, UBUNTU-CVE-2025-54351

## What is CVE-2025-54351?

CVE-2025-54351 is a high-severity memory corruption vulnerability in ES iperf3, published on 3 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In iperf before 3.19.1, net.c has a buffer overflow when --skip-rx-copy is used (for MSG_TRUNC in recv).

Weakness: CWE-420 (Unprotected Alternate Channel)

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

It affects 1 product.


Products: Es Iperf3.

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

Upgrade to a fixed version.

## Is CVE-2025-54351 being exploited?

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

## Other vulnerabilities in ES iperf3

- [CVE-2024-53580](https://insights.sbomify.com/CVE-2024-53580/): Null dereference in n/a (high 7.5)
- [CVE-2025-54349](https://insights.sbomify.com/CVE-2025-54349/): Memory corruption in iperf3 (medium 6.5)
- [CVE-2024-26306](https://insights.sbomify.com/CVE-2024-26306/): Information disclosure in n/a (medium 5.9)
- [CVE-2023-7250](https://insights.sbomify.com/CVE-2023-7250/): Iperf3: possible denial of service (medium 5.3)
- [CVE-2025-54350](https://insights.sbomify.com/CVE-2025-54350/): Denial of service in iperf3 (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54351 and fix it if it is affected.

What it is: CVE-2025-54351 is a high-severity memory corruption vulnerability in ES iperf3, published on 3 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54351 in the wild and no public exploit code.

Affected product: ES iperf3. 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-54351/ (Markdown: https://insights.sbomify.com/CVE-2025-54351/index.md)
```

## Sources

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

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