CVE-2026-71218

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-08-11. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity53% × 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, 2026
Patch available. Sources: redhat.
redhat

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

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

Vendor 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.

  1. 2026-08-21 04:58 UTCEG score recompute
  2. 2026-08-21 04:58 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 03:21 UTCEG score recompute
  5. 2026-08-20 03:21 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 01:43 UTCEG score recompute
  8. 2026-08-19 01:42 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 00:05 UTCEG score recompute
  12. 2026-08-18 00:05 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 22:27 UTCEG score recompute
  15. 2026-08-16 22:27 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:15 UTCEPSS rescore
  19. 2026-08-15 20:51 UTCEG score recompute
  20. 2026-08-15 20:51 UTCGHSA enrichment
  21. 2026-08-15 01:31 UTCEPSS rescore
  22. 2026-08-14 19:15 UTCEG score recompute
  23. 2026-08-14 19:15 UTCGHSA enrichment
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 17:38 UTCGHSA enrichment
Show 14 more
  1. 2026-08-12 16:00 UTCEG score recompute
  2. 2026-08-12 16:00 UTCGHSA enrichment
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 14:24 UTCEG score recompute
  5. 2026-08-11 14:24 UTCGHSA enrichment
  6. 2026-08-11 13:32 UTCEG score recompute
  7. 2026-08-11 13:32 UTCGHSA enrichment
  8. 2026-08-11 11:24 UTCEG score recompute
  9. 2026-08-11 11:24 UTCGHSA enrichment
  10. 2026-08-11 10:42 UTCEG score recompute
  11. 2026-08-11 10:42 UTCGHSA enrichment
  12. 2026-08-11 09:26 UTCEG score recompute
  13. 2026-08-11 09:13 UTCEG score recompute
  14. 2026-08-11 09:13 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71218?
CVE-2026-71218 is a medium vulnerability published on August 11, 2026. 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…
When was CVE-2026-71218 disclosed?
CVE-2026-71218 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71218 actively exploited?
CVE-2026-71218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.3% of all scored CVEs.
What is the CVSS score of CVE-2026-71218?
CVE-2026-71218 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-71218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71218, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-71218

Explore →

Is Your Infrastructure Affected by CVE-2026-71218?

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