Finding and attribution
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.
Product: Red Hat Red Hat Enterprise Linux 10. AI system: AISLE AI-native discovery engine (model/version not disclosed). Team / organization: AISLE.
CVE identifiers: CVE-2026-71217.
AI and human contribution (source account): AISLE’s CVE Discoveries index lists this CVE among those its AI-native engine discovered, and the individual AISLE page says “Discovered by AISLE”. The CNA record states “This issue was discovered by Found by AISLE in partnership with Red Hat.”; a credited human name is not itself AI attribution, which rests on AISLE’s page. The model/version and the division of work between the engine and human researchers are not disclosed.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: Public CVE disclosure is dated 2026-08-11. AISLE’s case page timeline shows 2026-08-11, used as the AI-attribution date. The cited sources establish an assigned vulnerability, not exploitation in the wild or zero-day status.
Remediation status: fix documented. Confirm the distribution-specific backport before relying on a version number.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 11 Aug 2026. AI attribution dated 11 Aug 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 7.5. Documented technical effects: Not available.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-71217: CVSS 3.1 · 7.5 (High) ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. redhat (CNA; CVE Program record) · checked 17 Nov 2026.
Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.
Documented fix: Confirm the distribution-specific backport before relying on a version number.