CVE-2026-111066

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

GHSA-9xw5-w5jj-pvcg ↗EUVD-2026-104482 ↗

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.
aio-libs aiohttp >=2, < 3.14.4
fixed in 3.14.4
CWE-400 Uncontrolled Resource Consumption
ETK-2026-2096Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/aiohttp
1d 11h 32msince last run
7mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+7h19m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

aiohttp versions 2.0.0 through 3.14.3 can retain file descriptors while processing multipart requests. An unauthenticated remote attacker may exhaust available descriptors if the application handles multipart input with Request.post().

mitigation

Upgrade aiohttp to version 3.14.4. Until upgrades are complete, restrict unauthenticated access to endpoints that accept multipart requests and use Request.post().

fixed in 3.14.4

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.
contextual
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.38%30th percentile
agent run time
7m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 16:59Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-19 16:59Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2096",
  "cve_id": "CVE-2026-111066",
  "display_id": "CVE-2026-111066",
  "ghsa_id": "GHSA-9xw5-w5jj-pvcg",
  "euvd_id": "EUVD-2026-104482",
  "status": "published",
  "anchor_state": "anchored",
  "title": "File descriptor exhaustion in aiohttp multipart processing",
  "summary": "aiohttp versions 2.0.0 through 3.14.3 can retain file descriptors while processing multipart requests. An unauthenticated remote attacker may exhaust available descriptors if the application handles multipart input with Request.post().",
  "mitigation": "Upgrade aiohttp to version 3.14.4. Until upgrades are complete, restrict unauthenticated access to endpoints that accept multipart requests and use Request.post().",
  "vendor": "aio-libs",
  "product": "aiohttp",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">=2, < 3.14.4"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "3.14.4"
      ],
      "package_name": "aiohttp",
      "purl": "pkg:pypi/aiohttp"
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0038,
  "epss_percentile": 0.3068,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 6.9560452,
  "t0_at": "2026-10-19T16:59:47.217000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T16:59:47.217000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T16:59:47.217000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111066"
    }
  }
}

published 2026-10-20 00:11Z
last change 2026-10-21 11:18Z

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.