How severe is CVE-2026-111064?

No CVSS score has been assigned to CVE-2026-111064 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-111064?

CVE-2026-111064 affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-111064?

Update aiohttp to 3.14.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-111064 is resolved across your whole dependency graph.

How do I detect CVE-2026-111064 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aiohttp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-111064 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2026-111064 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-111064 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-111064?

CVE-2026-111064 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-111064?

CVE-2026-111064 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-111064 published, and has it been updated?

CVE-2026-111064 was published on October 19, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-111064 — aiohttp

Fix: aio-libs/aiohttp@be84682

CVE-2026-111064 is a CWE-770 vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below.

aiohttp server lacks an initial request/header timeout

Also known asGHSA-5wr8-gcqf-gqf3

Published

Oct 19, 2026

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍aiohttp

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, keepalive timeout handling is absent during the initial portion of a request. An attacker can keep an idle connection open indefinitely before sending any request data, consuming server connection capacity. This issue is fixed in version 3.14.4.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`aiohttp`	all versions	3.14.4`pip install --upgrade 'aiohttp==3.14.4'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aiohttp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aiohttp to 3.14.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-111064 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This flaw affects products that run an aiohttp server exposed to untrusted clients. Products that use aiohttp only as an HTTP client are not affected.

Workaround published by Red Hat

--- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce initial keep-alive timeouts and first-request deadlines on newly established HTTP connections within aiohttp: upgrade to aiohttp 3.14.4 (or the fixed Ansible Automation Platform 24/Lightspeed Rhel/Rhoai/Odh Caikit Tgis Serving Rhel/Python3.11 Aiohttp/Koku/Exploit…

Source: Red Hat security advisory for CVE-2026-111064 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-111064 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works