A flaw was found in iperf3. A remote attacker can exploit this vulnerability by sending crafted control-channel JSON with oversized numeric parameters, such as parallel and len, which are not properly validated by the server. This improper input validation can lead to excessive stream and thread creation, as well as large buffer allocations, causing resource exhaustion. Consequently, this can result in a Denial of Service (DoS) on the affected iperf3 server.
CVE-2026-71217
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
August 11, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 11, 20262460984 – (CVE-2026-71217) CVE-2026-71217 iperf3: iperf3 server accepts unbounded peer-controlled JSON parameters enabling remote denial of service via resource exhaustion
https://bugzilla.redhat.com/show_bug.cgi?id=2460984CVE-2026-71217 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-71217Vendor Advisories for CVE-2026-71217(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 31× in last 7d / 49× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 00:30 UTCEG score recompute
- 2026-08-21 00:30 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 12:05 UTCGHSA enrichment
- 2026-08-19 23:39 UTCEG score recompute
- 2026-08-19 23:39 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 11:15 UTCGHSA enrichment
- 2026-08-18 22:47 UTCEG score recompute
- 2026-08-18 22:47 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 10:16 UTCGHSA enrichment
- 2026-08-17 21:51 UTCEG score recompute
- 2026-08-17 21:50 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 09:22 UTCGHSA enrichment
- 2026-08-16 20:58 UTCEG score recompute
- 2026-08-16 20:58 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:33 UTCEG score recompute
- 2026-08-16 08:33 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 20:09 UTCGHSA enrichment
Show 24 moreShow fewer
- 2026-08-15 07:44 UTCEG score recompute
- 2026-08-15 07:44 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 19:19 UTCGHSA enrichment
- 2026-08-14 07:57 UTCEG score recompute
- 2026-08-14 07:57 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 19:32 UTCGHSA enrichment
- 2026-08-13 07:07 UTCGHSA enrichment
- 2026-08-12 18:37 UTCEG score recompute
- 2026-08-12 18:37 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 06:12 UTCGHSA enrichment
- 2026-08-11 17:45 UTCEG score recompute
- 2026-08-11 17:45 UTCGHSA enrichment
- 2026-08-11 16:26 UTCEG score recompute
- 2026-08-11 16:26 UTCGHSA enrichment
- 2026-08-11 11:24 UTCEG score recompute
- 2026-08-11 11:24 UTCGHSA enrichment
- 2026-08-11 10:22 UTCEG score recompute
- 2026-08-11 10:22 UTCGHSA enrichment
- 2026-08-11 09:26 UTCEG score recompute
- 2026-08-11 09:13 UTCEG score recompute
- 2026-08-11 09:13 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2026-71217?
When was CVE-2026-71217 disclosed?
Is CVE-2026-71217 actively exploited?
What is the CVSS score of CVE-2026-71217?
How do I remediate CVE-2026-71217?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71217
Is Your Infrastructure Affected by CVE-2026-71217?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.