CVE-2026-71218

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM 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 — 4 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.7%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/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
Severity53% × 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.7%
EPSS %ILE
50th
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 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(2)

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

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
iperf3—
  • every version up to 3.18-1: fixed in 3.18-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
iperf3—
  • every version up to 3.18-1: fixed in 3.18-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 83× 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 168 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

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 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.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71218?
CVE-2026-71218 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71218?
A fix for CVE-2026-71218 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71218 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-71218

Explore →

Is Your Infrastructure Affected by CVE-2026-71218?

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

Book a Demo →Browse All CVEs