{"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-34519 in the wild and no public exploit code.","fix":"Upgrade aiohttp to 3.13.4 or later.","what":"CVE-2026-34519 is a low-severity vulnerability in aio-libs aiohttp, published on 1 Apr 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-34519 and fix it if it is affected.\n\nWhat it is: CVE-2026-34519 is a low-severity vulnerability in aio-libs aiohttp, published on 1 Apr 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-34519 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aiohttp (PyPI): affected all versions; fixed in 3.13.4\n- aiohttp (PyPI): affected all versions; fixed in 3.13.4\n- aiohttp (PyPI): affected all versions; fixed in 3.13.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-34519/ (Markdown: https://insights.sbomify.com/CVE-2026-34519/index.md)","id":"CVE-2026-34519","markdown":"https://insights.sbomify.com/CVE-2026-34519/index.md","name":"CVE-2026-34519","record":{"aliases":["AZL-81776","CLEANSTART-2026-QH05676","CLEANSTART-2026-UK00522","DEBIAN-CVE-2026-34519","ECHO-abe8-b546-ad42","GHSA-mwh4-6h8g-pg8w","MINI-3732-999q-8jxg","MINI-483v-2mxj-76fh","MINI-78r4-c654-6m6v","MINI-jvp9-chq7-7vhp","MINI-qpm6-v6c7-h77w","MINI-vgcm-947h-hjm8","MINI-wgvx-gh79-9qvf","PYSEC-2026-2101","ROOT-APP-PYPI-CVE-2026-34519","UBUNTU-CVE-2026-34519"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python HTTP library","requires_auth":"none","summary":"Attackers can inject headers via the reason phrase in aiohttp responses, potentially leading to cache poisoning or XSS.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"aiohttp","vendor":"aiohttp"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"description":"AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, an attacker who controls the reason parameter when creating a Response may be able to inject extra headers or similar exploits. This issue has been patched in version 3.13.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: HTTP response splitting via \\r in reason phrase","id":"CVE-2026-34519","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"AIOHTTP's C parser (llhttp) accepts null bytes and control characters in response header values - header injection/security bypass","id":"CVE-2026-34520"},"packages":[{"ecosystem":"PyPI","fixed":["3.13.4"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":null,"source":"GHSA-mwh4-6h8g-pg8w"},{"ecosystem":"PyPI","fixed":["3.13.4"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":"pkg:pypi/aiohttp","source":"GHSA-mwh4-6h8g-pg8w"},{"ecosystem":"PyPI","fixed":["3.13.4"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":"pkg:pypi/aiohttp","source":"PYSEC-2026-2101"}],"prev":{"headline":"AIOHTTP: Cookie and Proxy-Authorization headers leaked on cross-origin redirect","id":"CVE-2026-34518"},"products":["aiohttp"],"published":"2026-04-01","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-04-02","vendors":["aio-libs"]},"summary":"Attackers can inject headers via the reason phrase in aiohttp responses, potentially leading to cache poisoning or XSS.","url":"https://insights.sbomify.com/CVE-2026-34519/"}