# libiperf0 3.7-3ubuntu0.1~esm2: libiperf0 3.7-3ubuntu0.1~esm2 for Ubuntu 20.04 LTS (focal)

libiperf0 3.7-3ubuntu0.1~esm2, released August 2, 2025, fixes 4 CVEs in libiperf0. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.

- Web page: https://patchblox.com/security/fix/linux/ubuntu-focal-libiperf0-3.7-3ubuntu0.1-esm2
- Platform: Linux
- Released: Aug 2, 2025
- Priority: High (Closes CVE-2024-53580, high severity)
- CVEs: 4, exploited: 0, on CISA KEV: 0

## Applies to

| Product | Release | Fixed in |
|---|---|---|
| [libiperf0](https://patchblox.com/security/data/product/linux/libiperf0.md) | Ubuntu 20.04 LTS (focal) | 3.7-3ubuntu0.1~esm2 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2024-53580](https://patchblox.com/security/data/cve/CVE-2024-53580.md) | High | iperf: Fixed a segmentation violation via the iperf_exchange_parameters() function | 7.5 | 0.0091 |  |
| [CVE-2025-54349](https://patchblox.com/security/data/cve/CVE-2025-54349.md) | High | In iperf before 3.19.1, iperf_auth.c has an off-by-one error and resultant heap-based buffer overflow. | 10.0 | 0.0047 |  |
| [CVE-2024-26306](https://patchblox.com/security/data/cve/CVE-2024-26306.md) | Routine | iperf: Fixed a vulnerability that could led to marvin attack if the authentication option is used | 5.9 | 0.0110 |  |
| [CVE-2025-54350](https://patchblox.com/security/data/cve/CVE-2025-54350.md) | Routine | In iperf before 3.19.1, iperf_auth.c has a Base64Decode assertion failure and application exit upon a malformed authentication attempt. | 5.3 | 0.0048 |  |

---

Data as of 2026-11-12T19:57:06Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.