{"answers":{"affected":"3 open source packages ship an affected version, including aiohttp. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-69226 in the wild and no public exploit code.","fix":"Upgrade aiohttp to 3.13.3 or later.","what":"CVE-2025-69226 is a medium-severity vulnerability in aio-libs aiohttp, published on 5 Jan 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-2025-69226 and fix it if it is affected.\n\nWhat it is: CVE-2025-69226 is a medium-severity vulnerability in aio-libs aiohttp, published on 5 Jan 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-2025-69226 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aiohttp (PyPI): affected all versions; fixed in 3.13.3\n- aiohttp (PyPI): affected all versions; fixed in 3.13.3\n- aiohttp (PyPI): affected all versions; fixed in 3.13.3\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-2025-69226/ (Markdown: https://insights.sbomify.com/CVE-2025-69226/index.md)","id":"CVE-2025-69226","markdown":"https://insights.sbomify.com/CVE-2025-69226/index.md","name":"CVE-2025-69226","record":{"aliases":["AZL-73503","AZL-73526","CLEANSTART-2026-GO71625","CLEANSTART-2026-PD75328","CLSA-2026-1791456836","CLSA-2026-1791528872","DEBIAN-CVE-2025-69226","ECHO-7081-d4cf-1bf4","GHSA-54jq-c3m8-4m76","MINI-gxhq-g2w8-v88g","MINI-qvvv-542r-5hp3","PYSEC-2026-1097","ROOT-APP-PYPI-CVE-2025-69226","UBUNTU-CVE-2025-69226"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Python HTTP library","requires_auth":"none","summary":"Attackers can brute-force internal static file path components in aiohttp applications using web.static(), leading to information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"aiohttp","vendor":"aiohttp"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Versions 3.13.2 and below enable an attacker to ascertain the existence of absolute path components through the path normalization logic for static files meant to prevent path traversal. If an application uses web.static() (not recommended for production deployments), it may be possible for an attacker to ascertain the existence of path components. This issue is fixed in version 3.13.3.","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 allows for a brute-force leak of internal static filepath components","id":"CVE-2025-69226","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"AIOHTTP vulnerable to DoS when bypassing asserts","id":"CVE-2025-69227"},"packages":[{"ecosystem":"PyPI","fixed":["3.13.3"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":null,"source":"GHSA-54jq-c3m8-4m76"},{"ecosystem":"PyPI","fixed":["3.13.3"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":"pkg:pypi/aiohttp","source":"GHSA-54jq-c3m8-4m76"},{"ecosystem":"PyPI","fixed":["3.13.3"],"introduced":["0"],"last_affected":[],"package":"aiohttp","purl":"pkg:pypi/aiohttp","source":"PYSEC-2026-1097"}],"prev":{"headline":"AIOHTTP Regex Mismatch Allows Unicode in ASCII-Only Protocol Fields","id":"CVE-2025-69225"},"products":["aiohttp"],"published":"2026-01-05","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-01-06","vendors":["aio-libs"]},"summary":"Attackers can brute-force internal static file path components in aiohttp applications using web.static(), leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2025-69226/"}