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%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(medium)
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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
iperf33.12-1 ... 3.20-2.1 (16 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
iperf3—3.18-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
iperf3—3.18-1—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 22× in last 7d / 90× 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 126 total refreshes for this CVE.

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

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 67.7% 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

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.

Start Free Scan →Browse All CVEs