{"answers":{"affected":"2 open source packages ship an affected version, including aiohttp.","exploited":"There is no known exploitation of CVE-2026-111064 in the wild and no public exploit code.","fix":"Upgrade aiohttp to 3.14.4 or later.","what":"CVE-2026-111064 is a high-severity denial of service vulnerability in aio-libs aiohttp, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-111064 and fix it if it is affected.\n\nWhat it is: CVE-2026-111064 is a high-severity denial of service vulnerability in aio-libs aiohttp, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-111064 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aiohttp (PyPI): affected all versions; fixed in 3.14.4\n- aiohttp (PyPI): affected all versions; fixed in 3.14.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-111064/ (Markdown: https://insights.sbomify.com/CVE-2026-111064/index.md)","id":"CVE-2026-111064","markdown":"https://insights.sbomify.com/CVE-2026-111064/index.md","name":"CVE-2026-111064","record":{"aliases":["AZL-109887","DEBIAN-CVE-2026-111064","ECHO-2d22-25db-f131","GHSA-5wr8-gcqf-gqf3","MINI-gqf2-9wpr-47rv","MINI-hq2w-7825-cr8m","MINI-rw7g-v5p8-gc5f","ROOT-APP-PYPI-CVE-2026-111064","UBUNTU-CVE-2026-111064"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python HTTP library","requires_auth":"none","summary":"Attackers can exhaust server connection capacity by keeping idle connections open indefinitely due to missing initial request timeout handling.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"aiohttp server lacks an initial request/header timeout","id":"CVE-2026-111064","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"AIOHTTP: Connector pool exhaustion via Max-Age overflow","id":"CVE-2026-111065"},"packages":[{"ecosystem":"PyPI","fixed":["3.14.4"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":null,"source":"GHSA-5wr8-gcqf-gqf3"},{"ecosystem":"PyPI","fixed":["3.14.4"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":"pkg:pypi/aiohttp","source":"GHSA-5wr8-gcqf-gqf3"}],"prev":{"headline":"AIOHTTP: Secure attribute not enforced for shared cookie","id":"CVE-2026-111063"},"products":["aiohttp"],"published":"2026-10-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["aio-libs"]},"summary":"Attackers can exhaust server connection capacity by keeping idle connections open indefinitely due to missing initial request timeout handling.","url":"https://insights.sbomify.com/CVE-2026-111064/"}