OESA-2026-3527 (CVE-2026-71217)
Vulnerability from osv_openeuler – Published: 2026-08-30 04:14 – Updated: 2026-08-30 04:14 – Source websiteIperf is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing, protocols, and buffers.
Security Fix(es):
A flaw was found in iperf3. A remote attacker can exploit this vulnerability by sending crafted control-channel JSON with oversized numeric parameters, such as parallel and len, which are not properly validated by the server. This improper input validation can lead to excessive stream and thread creation, as well as large buffer allocations, causing resource exhaustion. Consequently, this can result in a Denial of Service (DoS) on the affected iperf3 server.(CVE-2026-71217)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"iperf3-3.21-2.oe2403sp3.aarch64.rpm",
"iperf3-debuginfo-3.21-2.oe2403sp3.aarch64.rpm",
"iperf3-debugsource-3.21-2.oe2403sp3.aarch64.rpm",
"iperf3-devel-3.21-2.oe2403sp3.aarch64.rpm"
],
"noarch": [
"iperf3-help-3.21-2.oe2403sp3.noarch.rpm"
],
"src": [
"iperf3-3.21-2.oe2403sp3.src.rpm"
],
"x86_64": [
"iperf3-3.21-2.oe2403sp3.x86_64.rpm",
"iperf3-debuginfo-3.21-2.oe2403sp3.x86_64.rpm",
"iperf3-debugsource-3.21-2.oe2403sp3.x86_64.rpm",
"iperf3-devel-3.21-2.oe2403sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP3",
"name": "iperf3",
"purl": "pkg:rpm/openEuler/iperf3\u0026distro=openEuler-24.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.21-2.oe2403sp3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"iperf3-3.21-2.oe2403sp4.aarch64.rpm",
"iperf3-debuginfo-3.21-2.oe2403sp4.aarch64.rpm",
"iperf3-debugsource-3.21-2.oe2403sp4.aarch64.rpm",
"iperf3-devel-3.21-2.oe2403sp4.aarch64.rpm"
],
"noarch": [
"iperf3-help-3.21-2.oe2403sp4.noarch.rpm"
],
"src": [
"iperf3-3.21-2.oe2403sp4.src.rpm"
],
"x86_64": [
"iperf3-3.21-2.oe2403sp4.x86_64.rpm",
"iperf3-debuginfo-3.21-2.oe2403sp4.x86_64.rpm",
"iperf3-debugsource-3.21-2.oe2403sp4.x86_64.rpm",
"iperf3-devel-3.21-2.oe2403sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP4",
"name": "iperf3",
"purl": "pkg:rpm/openEuler/iperf3\u0026distro=openEuler-24.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.21-2.oe2403sp4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"iperf3-3.21-2.oe2003sp4.aarch64.rpm",
"iperf3-debuginfo-3.21-2.oe2003sp4.aarch64.rpm",
"iperf3-debugsource-3.21-2.oe2003sp4.aarch64.rpm",
"iperf3-devel-3.21-2.oe2003sp4.aarch64.rpm"
],
"noarch": [
"iperf3-help-3.21-2.oe2003sp4.noarch.rpm"
],
"src": [
"iperf3-3.21-2.oe2003sp4.src.rpm"
],
"x86_64": [
"iperf3-3.21-2.oe2003sp4.x86_64.rpm",
"iperf3-debuginfo-3.21-2.oe2003sp4.x86_64.rpm",
"iperf3-debugsource-3.21-2.oe2003sp4.x86_64.rpm",
"iperf3-devel-3.21-2.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "iperf3",
"purl": "pkg:rpm/openEuler/iperf3\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.21-2.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"iperf3-3.21-2.oe2203sp4.aarch64.rpm",
"iperf3-debuginfo-3.21-2.oe2203sp4.aarch64.rpm",
"iperf3-debugsource-3.21-2.oe2203sp4.aarch64.rpm",
"iperf3-devel-3.21-2.oe2203sp4.aarch64.rpm"
],
"noarch": [
"iperf3-help-3.21-2.oe2203sp4.noarch.rpm"
],
"src": [
"iperf3-3.21-2.oe2203sp4.src.rpm"
],
"x86_64": [
"iperf3-3.21-2.oe2203sp4.x86_64.rpm",
"iperf3-debuginfo-3.21-2.oe2203sp4.x86_64.rpm",
"iperf3-debugsource-3.21-2.oe2203sp4.x86_64.rpm",
"iperf3-devel-3.21-2.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "iperf3",
"purl": "pkg:rpm/openEuler/iperf3\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.21-2.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"iperf3-3.21-2.oe2403sp1.aarch64.rpm",
"iperf3-debuginfo-3.21-2.oe2403sp1.aarch64.rpm",
"iperf3-debugsource-3.21-2.oe2403sp1.aarch64.rpm",
"iperf3-devel-3.21-2.oe2403sp1.aarch64.rpm"
],
"noarch": [
"iperf3-help-3.21-2.oe2403sp1.noarch.rpm"
],
"src": [
"iperf3-3.21-2.oe2403sp1.src.rpm"
],
"x86_64": [
"iperf3-3.21-2.oe2403sp1.x86_64.rpm",
"iperf3-debuginfo-3.21-2.oe2403sp1.x86_64.rpm",
"iperf3-debugsource-3.21-2.oe2403sp1.x86_64.rpm",
"iperf3-devel-3.21-2.oe2403sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP1",
"name": "iperf3",
"purl": "pkg:rpm/openEuler/iperf3\u0026distro=openEuler-24.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.21-2.oe2403sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "Iperf is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing, protocols, and buffers.\r\n\r\nSecurity Fix(es):\n\nA flaw was found in iperf3. A remote attacker can exploit this vulnerability by sending crafted control-channel JSON with oversized numeric parameters, such as `parallel` and `len`, which are not properly validated by the server. This improper input validation can lead to excessive stream and thread creation, as well as large buffer allocations, causing resource exhaustion. Consequently, this can result in a Denial of Service (DoS) on the affected iperf3 server.(CVE-2026-71217)",
"id": "OESA-2026-3527",
"modified": "2026-08-30T04:14:54Z",
"published": "2026-08-30T04:14:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3527"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-71217"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "iperf3 security update",
"upstream": [
"CVE-2026-71217"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.