CVE-2026-111064

validatedZero produced an exploit or a check.

GHSA-5wr8-gcqf-gqf3 ↗EUVD-2026-104480 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
pip aiohttp <= 3.14.3
fixed in 3.14.4
ETK-2026-2073Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/aiohttp
+1h36mTTV
19mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+96magent stopped
0
+30min
+60min
+90min

description

aiohttp releases before 3.14.4 do not enforce the expected timeout while an inbound request is starting. An attacker able to connect to an affected aiohttp server can hold connections open without sending request data, reducing capacity for legitimate clients.

mitigation

Upgrade aiohttp to version 3.14.4 or later. Until upgraded, place the service behind a reverse proxy and enforce appropriate connection keepalive limits.

fixed in 3.14.4

check
available
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.40%32nd percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 16:47Z
Δ 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

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

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

  1. 2026-10-19 16:47Z
    ghsa: trigger signal, started the run
  2. 2026-10-19 16:47Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2073",
  "cve_id": "CVE-2026-111064",
  "display_id": "CVE-2026-111064",
  "ghsa_id": "GHSA-5wr8-gcqf-gqf3",
  "euvd_id": "EUVD-2026-104480",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Connection resource exhaustion in aiohttp request handling",
  "summary": "aiohttp releases before 3.14.4 do not enforce the expected timeout while an inbound request is starting. An attacker able to connect to an affected aiohttp server can hold connections open without sending request data, reducing capacity for legitimate clients.",
  "mitigation": "Upgrade aiohttp to version 3.14.4 or later. Until upgraded, place the service behind a reverse proxy and enforce appropriate connection keepalive limits.",
  "vendor": "pip",
  "product": "aiohttp",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3.14.3"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "3.14.4"
      ],
      "package_name": "aiohttp",
      "purl": "pkg:pypi/aiohttp"
    }
  ],
  "cwes": null,
  "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.004,
  "epss_percentile": 0.3273,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 19.101330733333334,
  "t0_at": "2026-10-19T16:47:35.036000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-19T18:23:15.300648+00:00",
      "days": 0.06643824824074074,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T16:47:35.036000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-19T16:47:35.036000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T16:47:35.036000+00:00",
      "url": "https://github.com/advisories/GHSA-5wr8-gcqf-gqf3"
    }
  }
}

published 2026-10-19 18:04Z
last change 2026-10-21 14:01Z

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.