{"answers":{"affected":"3 open source packages ship an affected version, including aiohttp. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-54280 in the wild and no public exploit code.","fix":"Upgrade aiohttp to 3.14.1 or later.","what":"CVE-2026-54280 is a low-severity denial of service vulnerability in aio-libs aiohttp, published on 22 Jun 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-54280 and fix it if it is affected.\n\nWhat it is: CVE-2026-54280 is a low-severity denial of service vulnerability in aio-libs aiohttp, published on 22 Jun 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-54280 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aiohttp (PyPI): affected all versions; fixed in 3.14.1\n- aiohttp (PyPI): affected all versions; fixed in 3.14.1\n- aiohttp (PyPI): affected all versions; fixed in 3.14.1\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-54280/ (Markdown: https://insights.sbomify.com/CVE-2026-54280/index.md)","id":"CVE-2026-54280","markdown":"https://insights.sbomify.com/CVE-2026-54280/index.md","name":"CVE-2026-54280","record":{"aliases":["AZL-90662","CLEANSTART-2026-HP74400","CLEANSTART-2026-KI86994","DEBIAN-CVE-2026-54280","ECHO-d1ac-9337-96ab","GHSA-9x8q-7h8h-wcw9","MINI-22pq-c425-p99g","MINI-389j-h85v-3672","MINI-8ff5-9vmj-f8mg","MINI-8mc8-2w83-4m8h","MINI-994v-mqw5-x48r","MINI-cfv2-86mf-wq56","MINI-fr7w-7cpf-rqxp","MINI-h5fx-5wrr-h5pp","MINI-j67m-w5ff-h9h6","MINI-jxp5-74r8-w8g8","MINI-mh4w-8fvh-93hm","MINI-mx6m-5w8m-vm4r","MINI-q25q-jwr6-fjfq","MINI-qvqf-q8ff-v8r2","MINI-r6jv-mcxc-mxg7","MINI-rgr3-7g46-rhj6","MINI-x47r-6rh7-xprc","PYSEC-2026-2113","ROOT-APP-PYPI-CVE-2026-54280","UBUNTU-CVE-2026-54280"],"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 cause resource starvation by triggering mid-body disconnects, preventing proper closure of file resources in the aiohttp library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"aiohttp","vendor":"aiohttp"}],"cvss":{"score":1.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-404","name":"Improper Resource Shutdown or Release"}],"description":"AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, payload resources are not closed correctly when a client disconnects in the middle of a write. If a payload is using an open file or similar limited resource, then an attacker may be able to cause resource starvation temporarily until garbage collection or similar closes the file. This vulnerability is fixed in 3.14.1.","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: Payload Response Resources Are Not Closed After Mid-Body Disconnect","id":"CVE-2026-54280","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Nest: Middleware Bypass on Fastify via Trailing Slash","id":"CVE-2026-54281"},"packages":[{"ecosystem":"PyPI","fixed":["3.14.1"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":null,"source":"GHSA-9x8q-7h8h-wcw9"},{"ecosystem":"PyPI","fixed":["3.14.1"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":"pkg:pypi/aiohttp","source":"GHSA-9x8q-7h8h-wcw9"},{"ecosystem":"PyPI","fixed":["3.14.1"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":"pkg:pypi/aiohttp","source":"PYSEC-2026-2113"}],"prev":{"headline":"AIOHTTP: Host-Only Cookies Become Domain Cookies After CookieJar Persistence","id":"CVE-2026-54279"},"products":["aiohttp"],"published":"2026-06-22","related":[{"cvss_score":8.7,"headline":"aiohttp memory leak when middleware is enabled when requesting a resource with a non-allowed method","id":"CVE-2024-52303","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":7.5,"headline":"AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb","id":"CVE-2025-69223","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":7.5,"headline":"Denial of service when trying to parse malformed POST requests in aiohttp","id":"CVE-2024-30251","kev_date_added":null,"published":"2024-05-02"},{"cvss_score":7.2,"headline":"aiohttp's ClientSession is vulnerable to CRLF injection via version","id":"CVE-2023-49081","kev_date_added":null,"published":"2023-11-30"},{"cvss_score":6.9,"headline":"AIOHTTP: Uncapped memory usage possible through aiohttp allowing unlimited trailer headers","id":"CVE-2026-22815","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":6.6,"headline":"AIOHTTP: HTTP/1 Pipelined Requests Queue Without Limit","id":"CVE-2026-54273","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":6.6,"headline":"AIOHTTP: Incomplete websocket frame payloads bypass memory limits","id":"CVE-2026-54274","kev_date_added":null,"published":"2026-06-22"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["aio-libs"]},"summary":"Attackers can cause resource starvation by triggering mid-body disconnects, preventing proper closure of file resources in the aiohttp library.","url":"https://insights.sbomify.com/CVE-2026-54280/"}