# CVE-2025-54349: Memory corruption in iperf3 > An off-by-one error in iperf allows heap-based buffer overflows, potentially enabling remote code execution or denial of service. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/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:** 3 Nov 2025 - **Also known as:** ALPINE-CVE-2025-54349, ALSA-2026:1592, ALSA-2026:1595, ALSA-2026:1597, AZL-66060, AZL-66065, BELL-CVE-2025-54349, DEBIAN-CVE-2025-54349, GHSA-8xx8-qrh3-q8mq, JLSEC-2026-762, RHSA-2026:1592, RHSA-2026:1595, RHSA-2026:1597, RHSA-2026:1760, RHSA-2026:1773, RHSA-2026:1881, RHSA-2026:1882, RHSA-2026:1967, RHSA-2026:2328, RHSA-2026:2329, RHSA-2026:2448, RHSA-2026:2449, RLSA-2026:1592, RLSA-2026:1595, RLSA-2026:1597, UBUNTU-CVE-2025-54349 ## What is CVE-2025-54349? CVE-2025-54349 is a medium-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, iperf_auth.c has an off-by-one error and resultant heap-based buffer overflow. Weakness: CWE-193 (Off-by-one Error) ## Which versions are affected by CVE-2025-54349? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `iperf3` | AlmaLinux:10 | All versions | 3.17.1-5.el10_1 | | `iperf3` | AlmaLinux:8 | All versions | 3.5-12.el8_10 | | `iperf3` | AlmaLinux:9 | All versions | 3.9-14.el9_7.1 | | `iperf3` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.17.1-5.el10_1 | | `iperf3-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.17.1-5.el10_1 | | `iperf3-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.17.1-5.el10_1 | | `iperf3` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-12.el8_10 | | `iperf3-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-12.el8_10 | | `iperf3-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.5-12.el8_10 | | `iperf3` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-14.el9_7.1 | | `iperf3-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-14.el9_7.1 | | `iperf3-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.9-14.el9_7.1 | | `iperf3` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.17.1-4.el10_0.1 | | `iperf3-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.17.1-4.el10_0.1 | | `iperf3-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.17.1-4.el10_0.1 | | `iperf3` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2.2 | | `iperf3-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2.2 | | `iperf3-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.5-4.el8_2.2 | | `iperf3` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4.2 | | `iperf3-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4.2 | | `iperf3-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.5-7.el8_4.2 | | `iperf3` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.5-7.el8_6.2 | | `iperf3-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.5-7.el8_6.2 | | `iperf3-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.5-7.el8_6.2 | | `iperf3` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.5-7.el8_6.2 | | `iperf3-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.5-7.el8_6.2 | | `iperf3-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:3.5-7.el8_6.2 | | `iperf3` | Red Hat:rhel_e4s:8.8::appstream | All versions | 0:3.5-7.el8_8.2 | | `iperf3-debuginfo` | Red Hat:rhel_e4s:8.8::appstream | All versions | 0:3.5-7.el8_8.2 | | `iperf3-debugsource` | Red Hat:rhel_e4s:8.8::appstream | All versions | 0:3.5-7.el8_8.2 | | `iperf3` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.9-10.el9_0.2 | | `iperf3-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.9-10.el9_0.2 | | `iperf3-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.9-10.el9_0.2 | | `iperf3` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:3.9-10.el9_2.2 | | `iperf3-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:3.9-10.el9_2.2 | | `iperf3-debugsource` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:3.9-10.el9_2.2 | | `iperf3` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.9-11.el9_4.2 | | `iperf3-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.9-11.el9_4.2 | | `iperf3-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.9-11.el9_4.2 | | `iperf3` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:3.9-14.el9_6.1 | Products: Es Iperf3. ## How do I fix CVE-2025-54349? Upgrade to a fixed version. ## Is CVE-2025-54349 being exploited? There is no known exploitation of CVE-2025-54349 in the wild and no public exploit code. ## Other vulnerabilities in ES iperf3 - [CVE-2025-54351](https://insights.sbomify.com/CVE-2025-54351/): Memory corruption in iperf3 (high 8.9) - [CVE-2024-53580](https://insights.sbomify.com/CVE-2024-53580/): Null dereference in n/a (high 7.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-54349 and fix it if it is affected. What it is: CVE-2025-54349 is a medium-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-54349 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-54349/ (Markdown: https://insights.sbomify.com/CVE-2025-54349/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54349 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54349 - OSV: https://osv.dev/vulnerability/CVE-2025-54349 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-54349/ Summaries are generated and may contain mistakes; the official description above is the record.