{"answers":{"affected":"2 open source packages ship an affected version, including aiohttp.","exploited":"There is no known exploitation of CVE-2026-111750 in the wild and no public exploit code.","fix":"Upgrade aiohttp to 3.14.4 or later.","what":"CVE-2026-111750 is a medium-severity 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-111750 and fix it if it is affected.\n\nWhat it is: CVE-2026-111750 is a medium-severity 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-111750 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-111750/ (Markdown: https://insights.sbomify.com/CVE-2026-111750/index.md)","id":"CVE-2026-111750","markdown":"https://insights.sbomify.com/CVE-2026-111750/index.md","name":"CVE-2026-111750","record":{"aliases":["AZL-110695","DEBIAN-CVE-2026-111750","ECHO-b67a-7679-1b63","GHSA-pqxq-w44r-73xw","MINI-33gh-gj3f-7hg6","MINI-vcfv-f876-3mjm","MINI-xp92-5vjj-wcmq","UBUNTU-CVE-2026-111750"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Python HTTP library","requires_auth":"none","summary":"An attacker can smuggle HTTP requests in AIOHTTP when using the pure Python parser, bypassing intermediary security controls.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the pure Python parser accepts ambiguous HTTP request framing. An unauthenticated attacker can consequently smuggle requests when an application uses AIOHTTP_NO_EXTENSIONS or otherwise runs without a standard wheel and an intermediary interprets the framing differently. 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: Pure-Python parser request smuggling","id":"CVE-2026-111750","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"follow-redirects sensitiveHeaders regex escaping can expose credential headers","id":"CVE-2026-111755"},"packages":[{"ecosystem":"PyPI","fixed":["3.14.4"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":null,"source":"GHSA-pqxq-w44r-73xw"},{"ecosystem":"PyPI","fixed":["3.14.4"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":"pkg:pypi/aiohttp","source":"GHSA-pqxq-w44r-73xw"}],"prev":{"headline":"AIOHTTP: Cookie from subdomain can remove Host-Only Scope from existing cookies","id":"CVE-2026-111749"},"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":"An attacker can smuggle HTTP requests in AIOHTTP when using the pure Python parser, bypassing intermediary security controls.","url":"https://insights.sbomify.com/CVE-2026-111750/"}