Linux ·
openSUSE Leap · Security advisory · November 7, 2026
openSUSE Leap · Security advisory · November 7, 2026OPENSUSE-SU-2026:22090-1: iperf security update
OPENSUSE-SU-2026:22090-1, released November 7, 2026, fixes 5 CVEs in iperf (version 3.21-160000.1.1). None of them is reported as exploited. Patch Radar priority: Urgent.
Urgent
CVEs closed
5
1 rated Critical
Exploited
0
None reported
Highest CVSS
7.5
Base score, 0 to 10
Highest EPSS
0.0064
50th percentile
Priority of the 5 CVEs
Patch now 0
Urgent 1
High 2
Routine 2
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| iperf | opensuse-leap 16.0 | 3.21-160000.1.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Urgent | CVE-2026-101276 | iperf3 3.21 (esnet/iperf) contains a remote, unauthenticated heap use-after-free: the server's per-test watchdog server_timer_proc() frees streams without cancelling/joining their worker threads, so a blocked worker dereferences a freed iperf_stream; fixed in 3.22. | n/a | 0.0040 | None reported |
| High | CVE-2026-71217 | Iperf3: iperf3 server accepts unbounded peer-controlled json parameters enabling remote denial of service via resource exhaustion | 7.5 | 0.0064 | None reported |
| High | CVE-2026-102253 | iperf3 < 3.22 UDP Receive Worker Infinite Loop DoS | 7.5 | 0.0043 | None reported |
| Routine | CVE-2026-71218 | Iperf3: unbounded peer-controlled allocation in iperf3 json_read() allows unauthenticated remote memory exhaustion | 5.3 | 0.0038 | None reported |
| Routine | CVE-2026-101283 | iperf3: iperf3 3.20–3.21 (esnet/iperf) has a pre-auth heap buffer overflow in decrypt_rsa_message(): a 256-byte RSA buffer is... | n/a | 0.0038 | None reported |
Showing 1 to 5 of 5
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
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.