CVE-2026-71217

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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 computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

August 31, 2026

Advisory Details (2)

Auto-updated Aug 11, 2026
Patch available. Sources: redhat.
redhat

2460984 – (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=2460984
redhat Patch Available

CVE-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-71217

Vendor Advisories for CVE-2026-71217(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatiperf3-0:3.17.1-6.el10_2.12026-08-31redhat
redhatiperf3-0:3.5-12.el8_10.12026-08-31redhat
redhatiperf3-0:3.9-17.el9_8.12026-08-31redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
iperf33.12-1 ... 3.20-2.1 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
iperf33.18-2 ... 3.20-2.1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
iperf33.18-2 ... 3.20-2.1 (6 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 26× in last 7d / 132× 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.

Showing the most recent 100 of 268 total refreshes for this CVE.

  1. 2026-10-04 22:47 UTCVendor advisory
  2. 2026-10-04 22:47 UTCGHSA enrichment
  3. 2026-10-04 10:12 UTCVendor advisory
  4. 2026-10-04 10:12 UTCGHSA enrichment
  5. 2026-10-03 21:34 UTCEG score recompute
  6. 2026-10-03 21:34 UTCVendor advisory
  7. 2026-10-03 21:34 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 22:29 UTCEG score recompute
  10. 2026-10-02 22:29 UTCVendor advisory
  11. 2026-10-02 22:29 UTCGHSA enrichment
  12. 2026-10-02 17:56 UTCEPSS rescore
  13. 2026-10-02 08:47 UTCEG score recompute
  14. 2026-10-02 08:47 UTCVendor advisory
  15. 2026-10-02 08:47 UTCGHSA enrichment
  16. 2026-10-01 19:50 UTCEPSS rescore
  17. 2026-10-01 10:53 UTCVendor advisory
  18. 2026-10-01 10:53 UTCGHSA enrichment
  19. 2026-09-30 22:22 UTCEG score recompute
  20. 2026-09-30 22:22 UTCVendor advisory
  21. 2026-09-30 22:22 UTCGHSA enrichment
  22. 2026-09-30 15:03 UTCEPSS rescore
  23. 2026-09-29 05:18 UTCEG score recompute
  24. 2026-09-29 05:18 UTCVendor advisory
  25. 2026-09-29 05:18 UTCGHSA enrichment
Show 75 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 02:21 UTCEG score recompute
  3. 2026-09-28 02:21 UTCVendor advisory
  4. 2026-09-28 02:21 UTCGHSA enrichment
  5. 2026-09-27 13:48 UTCEPSS rescore
  6. 2026-09-27 11:03 UTCEG score recompute
  7. 2026-09-27 11:03 UTCVendor advisory
  8. 2026-09-27 11:03 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-25 03:57 UTCEG score recompute
  11. 2026-09-25 03:57 UTCVendor advisory
  12. 2026-09-25 03:57 UTCGHSA enrichment
  13. 2026-09-24 02:03 UTCEG score recompute
  14. 2026-09-24 02:03 UTCVendor advisory
  15. 2026-09-24 02:03 UTCGHSA enrichment
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 13:38 UTCVendor advisory
  18. 2026-09-23 13:38 UTCGHSA enrichment
  19. 2026-09-23 01:11 UTCEG score recompute
  20. 2026-09-23 01:11 UTCVendor advisory
  21. 2026-09-23 01:11 UTCGHSA enrichment
  22. 2026-09-22 12:45 UTCVendor advisory
  23. 2026-09-22 12:45 UTCGHSA enrichment
  24. 2026-09-22 00:20 UTCEG score recompute
  25. 2026-09-22 00:20 UTCVendor advisory
  26. 2026-09-22 00:20 UTCGHSA enrichment
  27. 2026-09-21 21:09 UTCEPSS rescore
  28. 2026-09-21 11:02 UTCEG score recompute
  29. 2026-09-21 11:02 UTCVendor advisory
  30. 2026-09-21 11:02 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEPSS rescore
  32. 2026-09-20 19:43 UTCVendor advisory
  33. 2026-09-20 19:43 UTCGHSA enrichment
  34. 2026-09-20 05:41 UTCVendor advisory
  35. 2026-09-20 05:41 UTCGHSA enrichment
  36. 2026-09-19 17:16 UTCEG score recompute
  37. 2026-09-19 17:16 UTCVendor advisory
  38. 2026-09-19 17:16 UTCGHSA enrichment
  39. 2026-09-19 03:17 UTCEG score recompute
  40. 2026-09-19 03:17 UTCVendor advisory
  41. 2026-09-19 03:17 UTCGHSA enrichment
  42. 2026-09-18 19:28 UTCEPSS rescore
  43. 2026-09-18 14:53 UTCVendor advisory
  44. 2026-09-18 14:53 UTCGHSA enrichment
  45. 2026-09-18 02:28 UTCEG score recompute
  46. 2026-09-18 02:28 UTCVendor advisory
  47. 2026-09-18 02:28 UTCGHSA enrichment
  48. 2026-09-17 14:03 UTCVendor advisory
  49. 2026-09-17 14:03 UTCGHSA enrichment
  50. 2026-09-17 00:39 UTCEG score recompute
  51. 2026-09-17 00:39 UTCVendor advisory
  52. 2026-09-17 00:39 UTCGHSA enrichment
  53. 2026-09-16 14:08 UTCEPSS rescore
  54. 2026-09-16 05:15 UTCEPSS rescore
  55. 2026-09-16 02:18 UTCVendor advisory
  56. 2026-09-16 02:18 UTCGHSA enrichment
  57. 2026-09-15 13:30 UTCEG score recompute
  58. 2026-09-15 13:30 UTCVendor advisory
  59. 2026-09-15 13:30 UTCGHSA enrichment
  60. 2026-09-15 03:12 UTCEPSS rescore
  61. 2026-09-14 22:50 UTCVendor advisory
  62. 2026-09-14 22:50 UTCGHSA enrichment
  63. 2026-09-14 10:25 UTCVendor advisory
  64. 2026-09-14 10:25 UTCGHSA enrichment
  65. 2026-09-13 22:01 UTCEG score recompute
  66. 2026-09-13 22:01 UTCVendor advisory
  67. 2026-09-13 22:01 UTCGHSA enrichment
  68. 2026-09-13 09:36 UTCVendor advisory
  69. 2026-09-13 09:36 UTCGHSA enrichment
  70. 2026-09-12 21:11 UTCEG score recompute
  71. 2026-09-12 21:11 UTCVendor advisory
  72. 2026-09-12 21:11 UTCGHSA enrichment
  73. 2026-09-12 15:02 UTCEPSS rescore
  74. 2026-09-12 08:46 UTCVendor advisory
  75. 2026-09-12 08:46 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-71217?
CVE-2026-71217 is a high vulnerability published on August 11, 2026. 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…
When was CVE-2026-71217 disclosed?
CVE-2026-71217 was first published on August 11, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71217 actively exploited?
CVE-2026-71217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71217?
CVE-2026-71217 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71217?
A fix for CVE-2026-71217 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71217 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71217

Explore →

Is Your Infrastructure Affected by CVE-2026-71217?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs