CVE-2026-128127

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

GHSA-24c4-3p7v-29cm ↗EUVD-2026-125759 ↗

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.
pip aiohttp <= 3.14.3
fixed in 3.14.4
ETK-2026-4590Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/aiohttp
2d 06h 44msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+66h40m
0
+2h
+4h
+6h
+8h
+10h

description

aiohttp versions before 3.14.4 can mishandle base64-encoded multipart parts when an application handler reads multipart request data. A remote attacker can bypass the configured request-size limit, causing excessive memory consumption or event-loop blocking; exploitation requires access to such a handler.

mitigation

Upgrade aiohttp to version 3.14.4 or later. Until upgraded, restrict access to endpoints that accept and process multipart uploads.

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.55%46th percentile
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 20:30Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-13 20:30Z
    ghsa: trigger signal, started the run
  2. 2026-11-13 20:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4590",
  "cve_id": "CVE-2026-128127",
  "display_id": "CVE-2026-128127",
  "ghsa_id": "GHSA-24c4-3p7v-29cm",
  "euvd_id": "EUVD-2026-125759",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded multipart base64 parsing in aiohttp",
  "summary": "aiohttp versions before 3.14.4 can mishandle base64-encoded multipart parts when an application handler reads multipart request data. A remote attacker can bypass the configured request-size limit, causing excessive memory consumption or event-loop blocking; exploitation requires access to such a handler.",
  "mitigation": "Upgrade aiohttp to version 3.14.4 or later. Until upgraded, restrict access to endpoints that accept and process multipart uploads.",
  "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": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0055,
  "epss_percentile": 0.4637,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.929756183333334,
  "t0_at": "2026-11-13T20:30:19.198000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T20:30:19.198000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T20:30:19.198000+00:00",
      "url": "https://github.com/advisories/GHSA-24c4-3p7v-29cm"
    }
  }
}

published 2026-11-16 14:59Z
last change 2026-11-18 21:43Z

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.