CVE-2025-54349

In iperf before 3.19.1, iperf_auth.c has an off-by-one error and resultant heap-based buffer overflow.

Published: 2025-08-03 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-54349 is rated Low Risk (35.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.36%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-54349

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.29% 0.36% +0.07%
2 2026-05-30 0.05% 0.29% +0.24%
3 2026-04-08 — 0.05% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-54349

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.2 3.7 [email protected]
10.0 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 6.0 [email protected]

Weakness enumeration for CVE-2025-54349

OS Trackers for CVE-2025-54349

vendor priority summary link
alpine — CVE-2025-54349: 1 source package rows (iperf3); 9 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 2, open 7. https://security.alpinelinux.org/vuln/CVE-2025-54349
debian not yet assigned CVE-2025-54349 not yet assigned priority: Debian including 1 source packages (iperf3), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-54349
redhat medium — https://access.redhat.com/security/cve/CVE-2025-54349
suse medium CVE-2025-54349 severity moderate: SUSE including 19 source package names (iperf-3.19.1-1.1, iperf-3.19.1-150000.3.15.1, …), 71 product×package rows across 21 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (21 product lines)): Fixed 71. https://www.suse.com/security/cve/CVE-2025-54349/
ubuntu medium CVE-2025-54349 medium priority: Ubuntu including 1 source packages (iperf3), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): released 5, not-affected 2, ignored 1. https://ubuntu.com/security/CVE-2025-54349

Affected software / configurations for CVE-2025-54349

Vendor Product Version Raw CPE
es iperf3 >= 3.2, < 3.19.1 cpe:2.3:a:es:iperf3:*:*:*:*:*:*:*:*

References for CVE-2025-54349

cvelogic Threat Intelligence