A flaw was found in iperf3. A remote unauthenticated attacker can exploit a vulnerability in the JSON_read() function, which accepts a peer-controlled message length and allocates memory without an upper bound. This allows the attacker to trigger excessive memory consumption, leading to a Denial of Service (DoS) through memory exhaustion, severe slowdown, or termination of the iperf3 service.
CVE-2026-71218
Score 5.3 from GitHub Security Advisory published 2026-08-11. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
August 11, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 11, 20262463003 – (CVE-2026-71218) CVE-2026-71218 iperf3: Unbounded peer-controlled allocation in iperf3 JSON_read() allows unauthenticated remote memory exhaustion
https://bugzilla.redhat.com/show_bug.cgi?id=2463003CVE-2026-71218 - 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-71218Vendor Advisories for CVE-2026-71218(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 23× in last 7d / 39× 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 04:58 UTCEG score recompute
- 2026-08-21 04:58 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 03:21 UTCEG score recompute
- 2026-08-20 03:21 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 01:43 UTCEG score recompute
- 2026-08-19 01:42 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 00:05 UTCEG score recompute
- 2026-08-18 00:05 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 22:27 UTCEG score recompute
- 2026-08-16 22:27 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 20:51 UTCEG score recompute
- 2026-08-15 20:51 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 19:15 UTCEG score recompute
- 2026-08-14 19:15 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 17:38 UTCGHSA enrichment
Show 14 moreShow fewer
- 2026-08-12 16:00 UTCEG score recompute
- 2026-08-12 16:00 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 14:24 UTCEG score recompute
- 2026-08-11 14:24 UTCGHSA enrichment
- 2026-08-11 13:32 UTCEG score recompute
- 2026-08-11 13:32 UTCGHSA enrichment
- 2026-08-11 11:24 UTCEG score recompute
- 2026-08-11 11:24 UTCGHSA enrichment
- 2026-08-11 10:42 UTCEG score recompute
- 2026-08-11 10:42 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
Frequently asked(5)
What is CVE-2026-71218?
When was CVE-2026-71218 disclosed?
Is CVE-2026-71218 actively exploited?
What is the CVSS score of CVE-2026-71218?
How do I remediate CVE-2026-71218?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71218
Is Your Infrastructure Affected by CVE-2026-71218?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.