CVE-2026-101283

waiting for further signalsZero needs more public information before it can validate it.

GHSA-pwcx-5qh6-2pxc ↗EUVD-2026-90389 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
esnet iperf3 3.20; 3.21
fixed in 3.22
CWE-122 Heap-based Buffer Overflow
ETK-2026-161, permanent identifier
20d 10h 37msince last run
52mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h13m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

iperf3 versions 3.20 through 3.21 contain a heap buffer overflow in RSA message decryption used during authentication handling. An unauthenticated remote client may trigger memory corruption by connecting to a vulnerable iperf3 service and supplying an oversized authentication token.

mitigation

Upgrade iperf3 to version 3.22 or later. Until upgrading, restrict network access to iperf3 services to trusted clients.

fixed in 3.22

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.28%19th percentile
agent run time
52m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 21:32Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-30 21:32Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-101283

{
  "etk_id": "ETK-2026-161",
  "cve_id": "CVE-2026-101283",
  "display_id": "CVE-2026-101283",
  "ghsa_id": "GHSA-pwcx-5qh6-2pxc",
  "euvd_id": "EUVD-2026-90389",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Pre-authentication heap buffer overflow in iperf3",
  "summary": "iperf3 versions 3.20 through 3.21 contain a heap buffer overflow in RSA message decryption used during authentication handling. An unauthenticated remote client may trigger memory corruption by connecting to a vulnerable iperf3 service and supplying an oversized authentication token.",
  "mitigation": "Upgrade iperf3 to version 3.22 or later. Until upgrading, restrict network access to iperf3 services to trusted clients.",
  "vendor": "esnet",
  "product": "iperf3",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "3.20",
        "3.21"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.22"
      ],
      "package_name": "iperf3",
      "purl": null
    }
  ],
  "cwes": [
    122
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0028,
  "epss_percentile": 0.1929,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 52.025238783333336,
  "t0_at": "2026-09-30T21:32:14.699000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T21:32:14.699000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T21:32:14.699000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-101283"
    }
  }
}

published 2026-09-30 21:52Z
last change 2026-10-21 07:48Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.