CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NHigh (8.7) in esnet iperf3. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain CVE-2026-102253 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102253?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102253?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102253 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| esnet iperf3 | from 3.14 before 3.22 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | iperf3 | no fix listed | DEBIAN-CVE-2026-102253 |
| Debian | 14 | iperf3 | 3.22-0.1 | DEBIAN-CVE-2026-102253 |
| Ubuntu | 26.04:LTS, 26.10, Pro:16.04:LTS and 4 more | iperf3 | no fix listed | UBUNTU-CVE-2026-102253 |
| Red Hat | enterprise_linux:10.2 | iperf3, iperf3-debuginfo, iperf3-debugsource | 0:3.17.1-6.el10_2.2 | RHSA-2026:88207 |
| Red Hat | enterprise_linux:10.3 | iperf3, iperf3-debuginfo, iperf3-debugsource | 0:3.21-2.el10_3.1 | RHSA-2026:98085 |
| SUSE | Enterprise Storage 7.1, Linux Enterprise Module for Package Hub 15 SP7 | iperf | 3.22-150000.3.18.1 | SUSE-SU-2026:4678-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | iperf | 3.21-160000.1.1 | SUSE-SU-2026:24234-1 |
| SUSE | Linux Micro Extras 6.2 | iperf | 3.21-160000.1.1 | SUSE-SU-2026:24178-1 |
| openSUSE | Leap 16.0 | iperf | 3.21-160000.1.1 | openSUSE-SU-2026:22090-1 |
| openSUSE | Tumbleweed | iperf | 3.22-1.1 | openSUSE-SU-2026:12060-1 |
| AlmaLinux | 10 | iperf3 | 3.17.1-6.el10_2.2 | ALSA-2026:88207 |
| AlmaLinux | 10 | iperf3 | 3.21-2.el10_3.1 | ALSA-2026:98085 |
| Rocky Linux | 10 | iperf3 | 0:3.17.1-6.el10_2.2 | RLSA-2026:88207 |
| Rocky Linux | 10 | iperf3, iperf3-debuginfo, iperf3-debugsource | 0:3.21-2.el10_3.1 | RLSA-2026:98085 |
| Azure Linux | 3 | iperf3 | 3.17.1-7 | AZL-105051 |
| Alpaquita | 23, 25, stream | iperf3 | 3.22-r0 | BELL-CVE-2026-102253 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpaquita.
Red Hat rates this Important.
This vulnerability is rated as Important severity for Red Hat because an unauthenticated remote attacker can trigger complete denial of service through severe CPU resource exhaustion without requiring elevated privileges. While iperf3 is predominantly invoked on demand for diagnostic network throughput benchmarking rather than deployed as a continuous background daemon, any active listener exposed to untrusted network traffic can be forced into an unresponsive state. The affected process ceases responding to control messages and requires manual administrative termination via SIGKILL, rendering benchmarking services unavailable.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | iperf3-0:3.17.1-6.el10_2.2 | Fixed 2026-10-22 | RHSA-2026:88207 |
| Red Hat Enterprise Linux 7 | iperf3 | Not affected | |
| Red Hat Enterprise Linux 8 | iperf3 | Not affected | |
| Red Hat Enterprise Linux 9 | iperf3 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102253.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.