Skip to content
Fencer Intel
critical 9.2

CVE-2026-101283 json

iperf3 3.20–3.21 (esnet/iperf) has a pre-auth heap buffer overflow in decrypt_rsa_message(): a 256-byte RSA buffer is BIO_read with the att…

published last mo. modified last mo. also EUVD-2026-90389

cvss
9.2
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

Summary

iperf3 3.20–3.21 (esnet/iperf) has a pre-auth heap buffer overflow in decrypt_rsa_message(): a 256-byte RSA buffer is BIO_read with the attacker-controlled ciphertext length (guard warns only), so an unauthenticated client overflows the heap via an oversized authtoken; fixed in 3.22

Patch / fix

  • iperf3 Debian 14 3.22-0.1

debian advisories DEBIAN-CVE-2026-101283

  • iperf SLE Module for Package Hub 15 SP7, Enterprise Storage 7.1 3.22-150000.3.18.1
  • iperf SLES 16.0, Linux Micro Extras 6.2, SLES for SAP applications 16.0 3.21-160000.1.1

suse advisories SUSE-SU-2026:4678-1SUSE-SU-2026:24178-1SUSE-SU-2026:24234-1

  • iperf openSUSE Leap 16.0 3.21-160000.1.1
  • iperf openSUSE Tumbleweed 3.22-1.1

opensuse advisories openSUSE-SU-2026:22090-1openSUSE-SU-2026:12060-1

Is CVE-2026-101283 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last mo.

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 9.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA 4.0 9.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • esnet iperf3

Classification

Weakness
  • CWE-122 Heap-based Buffer Overflow

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.