ETK-2026-2070Zero's internal tracking ID, independent of the CVE number.

validatedZero produced an exploit or a check.

GHSA-2g87-pp6c-29x5 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
awaiting cvepublic 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-2070Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:pypi/aiohttp
−1.3dTTV
10mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal +0hcheck available+0h41magent stopped
0
+12h
+24h
+36h

description

aiohttp can consume excessive CPU or memory while processing crafted HTTP requests. An attacker able to send requests to an application using a vulnerable aiohttp release could cause resource exhaustion.

mitigation

Upgrade aiohttp to version 3.14.4 or later. Restrict untrusted request access until the update is deployed.

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.
–
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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 check: a technique exists and was validated, 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 17:07Z
    ghsa: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/ETK-2026-2070

{
  "etk_id": "ETK-2026-2070",
  "cve_id": null,
  "display_id": "ETK-2026-2070",
  "ghsa_id": "GHSA-2g87-pp6c-29x5",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Resource exhaustion in aiohttp request handling",
  "summary": "aiohttp can consume excessive CPU or memory while processing crafted HTTP requests. An attacker able to send requests to an application using a vulnerable aiohttp release could cause resource exhaustion.",
  "mitigation": "Upgrade aiohttp to version 3.14.4 or later. Restrict untrusted request access until the update is deployed.",
  "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.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 10.4814096,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-10-19T17:48:37.257385+00:00",
      "days": -1.3494228479166668,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T02:11:47.426577+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-19T17:07:23+00:00",
      "days": -1.3780600861689816,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T02:11:47.426577+00:00",
      "url": "https://github.com/advisories/GHSA-2g87-pp6c-29x5"
    }
  }
}

published 2026-10-19 17:38Z
last change 2026-10-21 01:51Z

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.