CVE-2025-54349: In iperf before 3.19.1, iperf_auth.c has an off-by-one error and resultant heap-based buffer overflow.
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 iperf3 3.17.1-3 on Azure Linux 3.0 3.17.1-3; cbl2 iperf3 3.18-1 on CBL Mariner 2.0 3.18-2; cbl2 iperf3 3.18-2 on CBL Mariner 2.0 3.18-2.
- Severity is disputed: the assigning authority (CNA) scores it 6.5, NVD 10.0.
Add it to your regular patch cycle. Upgrade to azl3 iperf3 3.17.1-3 on Azure Linux 3.0 3.17.1-3; cbl2 iperf3 3.18-1 on CBL Mariner 2.0 3.18-2; cbl2 iperf3 3.18-2 on CBL Mariner 2.0 3.18-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- BDU:2025-12588
- ALSA-2026:1592
- ALSA-2026:1595
- ALSA-2026:1597
- DLA-4281-1
- openSUSE-SU-2025:15414-1
- RHSA-2026:1592
- RHSA-2026:1595
- RHSA-2026:1597
- RHSA-2026:1760
- RHSA-2026:1773
- RHSA-2026:1881
- RHSA-2026:1882
- RHSA-2026:1967
- RHSA-2026:2328
- RHSA-2026:2329
- RHSA-2026:2448
- RHSA-2026:2449
- RLSA-2026:1592
- RLSA-2026:1595
- Published
- Aug 2, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-193
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 10.0
- CNA · mitre
- 6.5
- 3.5 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| es | iperf3 | cpe:2.3:a:es:iperf3 |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.
ES iperf3
- before 3.19.1affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- es iperf33.2 and later · before 3.19.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | iperf3 | before 3.17.1-5.el10_1 | 3.17.1-5.el10_1 |
| AlmaLinux:8 | iperf3 | before 3.5-12.el8_10 | 3.5-12.el8_10 |
| AlmaLinux:9 | iperf3 | before 3.9-14.el9_7.1 | 3.9-14.el9_7.1 |
| Alpine:v3.22 | iperf3 | from 3.2 · before 3.19.1-r0 | 3.19.1-r0 |
| Debian:11 | iperf3 | before 3.9-1+deb11u3 | 3.9-1+deb11u3 |
| Debian:12 | iperf3 | before 3.12-1+deb12u2 | 3.12-1+deb12u2 |
| Debian:13 | iperf3 | before 3.18-2+deb13u1 | 3.18-2+deb13u1 |
| Debian:14 | iperf3 | before 3.19.1-1 | 3.19.1-1 |
| openSUSE:Leap 15.6 | iperf | before 3.19.1-150000.3.15.1 | 3.19.1-150000.3.15.1 |
| openSUSE:Tumbleweed | iperf | before 3.19.1-1.1 | 3.19.1-1.1 |
| Red Hat:enterprise_linux_eus:10.0 | iperf3 | before 0:3.17.1-4.el10_0.1 | 0:3.17.1-4.el10_0.1 |
| Red Hat:enterprise_linux_eus:10.0 | iperf3-debuginfo | before 0:3.17.1-4.el10_0.1 | 0:3.17.1-4.el10_0.1 |
| Red Hat:enterprise_linux_eus:10.0 | iperf3-debugsource | before 0:3.17.1-4.el10_0.1 | 0:3.17.1-4.el10_0.1 |
| Red Hat:enterprise_linux:10.1 | iperf3 | before 0:3.17.1-5.el10_1 | 0:3.17.1-5.el10_1 |
| Red Hat:enterprise_linux:10.1 | iperf3-debuginfo | before 0:3.17.1-5.el10_1 | 0:3.17.1-5.el10_1 |
| Red Hat:enterprise_linux:10.1 | iperf3-debugsource | before 0:3.17.1-5.el10_1 | 0:3.17.1-5.el10_1 |
| Red Hat:enterprise_linux:8::appstream | iperf3 | before 0:3.5-12.el8_10 | 0:3.5-12.el8_10 |
| Red Hat:enterprise_linux:8::appstream | iperf3-debuginfo | before 0:3.5-12.el8_10 | 0:3.5-12.el8_10 |
| Red Hat:enterprise_linux:8::appstream | iperf3-debugsource | before 0:3.5-12.el8_10 | 0:3.5-12.el8_10 |
| Red Hat:enterprise_linux:9::appstream | iperf3 | before 0:3.9-14.el9_7.1 | 0:3.9-14.el9_7.1 |
| Red Hat:enterprise_linux:9::appstream | iperf3-debuginfo | before 0:3.9-14.el9_7.1 | 0:3.9-14.el9_7.1 |
| Red Hat:enterprise_linux:9::appstream | iperf3-debugsource | before 0:3.9-14.el9_7.1 | 0:3.9-14.el9_7.1 |
| Red Hat:rhel_aus:8.2::appstream | iperf3 | before 0:3.5-4.el8_2.2 | 0:3.5-4.el8_2.2 |
| Red Hat:rhel_aus:8.2::appstream | iperf3-debuginfo | before 0:3.5-4.el8_2.2 | 0:3.5-4.el8_2.2 |
+26
Same product
es: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-4303The parse_string function in cjson.c in the cJSON library mishandles UTF8/16 strings, which allows remote attackers to cause a denial of…41Plan
- CVE-2025-54351In iperf before 3.19.1, net.c has a buffer overflow when --skip-rx-copy is used (for MSG_TRUNC in recv).40Plan
- CVE-2023-38403iperf3 before 3.14 allows peers to cause an integer overflow and heap corruption via a crafted length field.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-26306May 14, 2024 · iPerf3 before 3.17, when used with OpenSSL before 3.2.0 as a server with RSA authentication, allows a timing side channel in RSA decryption…23Monitor
- ← EarlierCVE-2024-53580Dec 18, 2024 · iperf v3.17.1 was discovered to contain a segmentation violation via the iperf_exchange_parameters() function.30Monitor
- Later →CVE-2025-54350Aug 2, 2025 · In iperf before 3.19.1, iperf_auth.c has a Base64Decode assertion failure and application exit upon a malformed authentication attempt.21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 iperf3 3.17.1-3 on Azure Linux 3.0 | 3.17.1-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 iperf3 3.18-1 on CBL Mariner 2.0 | 3.18-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 iperf3 3.18-2 on CBL Mariner 2.0 | 3.18-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:iperf3 | 3.5-12.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| alpine:iperf3 | 3.19.1-r0 · Alpine:v3.22 | Package registry (OSV) |
| debian:iperf3 | 3.12-1+deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:iperf | 3.19.1-150000.3.15.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:iperf3 | 0:3.5-12.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:iperf3-debuginfo | 0:3.5-12.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:iperf3-debugsource | 0:3.5-12.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:iperf3 | 0:3.5-12.el8_10 · Rocky Linux:8 | Package registry (OSV) |
| suse:iperf | 3.19.1-150000.3.15.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-193 · Off-by-one ErrorCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.