CVE-2025-54351: ES iperf3 · Unprotected Alternate Channel
Affects ES iperf3Source CVE Database V5
Not known to be exploited · CVSS 8.9 High.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 3 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ES iperf3 | Affected
| Fixed in– |
AI-suggested
European organizations should immediately audit their environments for iperf3 deployments, particularly versions prior to 3.19.1, and identify any instances where the --skip-rx-copy option is enabled. Until a patch is available, it is critical to disable the --skip-rx-copy option to prevent triggering the vulnerable code path. Network administrators should restrict access to iperf3 services using firewall rules or VPNs to limit exposure to untrusted networks. Monitoring network traffic for unusual or malformed packets targeting iperf3 ports can provide early detection of exploitation attempts. Organizations should also implement network segmentation to isolate performance testing tools from critical infrastructure. Once a patch is released, prompt application of updates is essential. Additionally, consider deploying intrusion detection systems with signatures tuned to detect attempts to exploit this buffer overflow. Conducting regular vulnerability scans and penetration tests focusing on iperf3 can help verify mitigation effectiveness.
Description
In iperf before 3.19.1, net.c has a buffer overflow when --skip-rx-copy is used (for MSG_TRUNC in recv).