{"ecosystem":"pypi","package":"aiohttp","version":null,"bugs":[{"id":420,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.3","bug_id":"osv:GHSA-6mq8-rvhq-8wgg","title":"AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb","description":"### Summary\nA zip bomb can be used to execute a DoS against the aiohttp server.\n\n### Impact\nAn attacker may be able to send a compressed request that when decompressed by aiohttp could exhaust the host's memory.\n\n------\n\nPatch: https://github.com/aio-libs/aiohttp/commit/2b920c39002cee0ec5b402581779bbaaf7c9138a","severity":"high","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-6mq8-rvhq-8wgg","labels":["CVE-2025-69223"],"created_at":"2026-04-19T04:31:29.634059+00:00","updated_at":"2026-04-19T04:31:29.634059+00:00"},{"id":416,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.9.4","bug_id":"osv:GHSA-5m98-qgg9-wh84","title":"aiohttp vulnerable to Denial of Service when trying to parse malformed POST requests","description":"### Summary\nAn attacker can send a specially crafted POST (multipart/form-data) request. When the aiohttp server processes it, the server will enter an infinite loop and be unable to process any further requests.\n\n### Impact\nAn attacker can stop the application from serving requests after sending a single request.\n\n-------\n\nFor anyone needing to patch older versions of aiohttp, the minimum diff needed to resolve the issue is (located in `_read_chunk_from_length()`):\n\n```diff\ndiff --git a/aiohttp/multipart.py b/aiohttp/multipart.py\nindex 227be605c..71fc2654a 100644\n--- a/aiohttp/multipart.py\n+++ b/aiohttp/multipart.py\n@@ -338,6 +338,8 @@ class BodyPartReader:\n         assert self._length is not None, \"Content-Length required for chunked read\"\n         chunk_size = min(size, self._length - self._read_bytes)\n         chunk = await self._content.read(chunk_size)\n+        if self._content.at_eof():\n+            self._at_eof = True\n         return chunk\n \n     async def _read_chunk_from_stream(self, size: int) -> bytes:\n```\n\nThis does however introduce some very minor issues with handling form data. So, if possible, it would be recommended to also backport the changes in:\nhttps://github.com/aio-libs/aiohttp/commit/cebe526b9c34dc3a3da9140409db63014bc4cf19\nhttps://github.com/aio-libs/aiohttp/commit/7eecdff163ccf029fbb1ddc9de4169d4aaeb6597\nhttps://github.com/aio-libs/aiohttp/commit/f21c6f2ca512a026ce7f0f6c6311f62d6a638866","severity":"high","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5m98-qgg9-wh84","labels":["CVE-2024-30251"],"created_at":"2026-04-19T04:31:29.630778+00:00","updated_at":"2026-04-19T04:31:29.630778+00:00"},{"id":415,"ecosystem":"pypi","package_name":"aiohttp","affected_version":"1.0.5","fixed_version":"3.9.2","bug_id":"osv:GHSA-5h86-8mv2-jq9f","title":"aiohttp is vulnerable to directory traversal","description":"### Summary\nImproperly configuring static resource resolution in aiohttp when used as a web server can result in the unauthorized reading of arbitrary files on the system.\n\n### Details\nWhen using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option 'follow_symlinks' can be used to determine whether to follow symbolic links outside the static root directory. When 'follow_symlinks' is set to True, there is no validation to check if a given file path is within the root directory.This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present.\n\ni.e. An application is only vulnerable with setup code like:\n```\napp.router.add_routes([\n    web.static(\"/static\", \"static/\", follow_symlinks=True),  # Remove follow_symlinks to avoid the vulnerability\n])\n```\n\n### Impact\nThis is a directory traversal vulnerability with CWE ID 22. When using aiohttp as a web server and enabling static resource resolution with `follow_symlinks` set to True, it can lead to this vulnerability. This vulnerability has been present since the introduction of the `follow_symlinks` parameter.\n\n### Workaround\nEven if upgrading to a patched version of aiohttp, we recommend following these steps regardless.\n\nIf using `follow_symlinks=True` outside of a restricted local development environment, disable the option immediately. This option is NOT needed to follow symlinks which point to a location _within_ the static root directory, it is _only_ intended to allow a symlink to break out of the static directory. Even with this CVE fixed, there is still a substantial risk of misconfiguration when using this option on a server that accepts requests from remote users.\n\nAdditionally, aiohttp has always recommended using a reverse proxy server (such as nginx) to handle static resources and _not_ to use these static resources in aiohttp for production environments. Doing so also protects against this vulnerability, and is why we expect the number of affected users to be very low.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/pull/8079/files","severity":"high","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5h86-8mv2-jq9f","labels":["CVE-2024-23334","PYSEC-2024-24"],"created_at":"2026-04-19T04:31:29.629778+00:00","updated_at":"2026-04-19T04:31:29.629778+00:00"},{"id":450,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"33ccdfb0a12690af5bb49bda2319ec0907fa7827","bug_id":"osv:PYSEC-2024-26","title":"PYSEC-2024-26: advisory","description":"aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Security-sensitive parts of the Python HTTP parser retained minor differences in allowable character sets, that must trigger error handling to robustly match frame boundaries of proxies in order to protect against injection of additional requests. Additionally, validation could trigger exceptions that were not handled consistently with processing of other malformed input.  Being more lenient than internet standards require could, depending on deployment environment, assist in request smuggling. The unhandled exception could cause excessive resource consumption on the application server and/or its logging facilities. This vulnerability exists due to an incomplete fix for CVE-2023-47627. Version 3.9.2 fixes this vulnerability.","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-8qpw-xqxj-h4r2","labels":["CVE-2024-23829","GHSA-8qpw-xqxj-h4r2"],"created_at":"2026-04-19T04:31:29.672299+00:00","updated_at":"2026-04-19T04:31:29.672299+00:00"},{"id":449,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"1c335944d6a8b1298baf179b7c0b3069f10c514b","bug_id":"osv:PYSEC-2024-24","title":"PYSEC-2024-24: advisory","description":"aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option 'follow_symlinks' can be used to determine whether to follow symbolic links outside the static root directory. When 'follow_symlinks' is set to True, there is no validation to check if reading a file is within the root directory. This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present.  Disabling follow_symlinks and using a reverse proxy are encouraged mitigations.  Version 3.9.2 fixes this issue.","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5h86-8mv2-jq9f","labels":["CVE-2024-23334","GHSA-5h86-8mv2-jq9f"],"created_at":"2026-04-19T04:31:29.671396+00:00","updated_at":"2026-04-19T04:31:29.671396+00:00"},{"id":448,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"e4ae01c2077d2cfa116aa82e4ff6866857f7c466","bug_id":"osv:PYSEC-2023-251","title":"PYSEC-2023-251: advisory","description":"aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Improper validation makes it possible for an attacker to modify the HTTP request (e.g. insert a new header) or even create a new HTTP request if the attacker controls the HTTP method. The vulnerability occurs only if the attacker can control the HTTP method (GET, POST etc.) of the request. If the attacker can control the HTTP version of the request it will be able to modify the request (request smuggling). This issue has been patched in version 3.9.0.","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-qvrw-v9rv-5rjx","labels":["CVE-2023-49082","GHSA-qvrw-v9rv-5rjx"],"created_at":"2026-04-19T04:31:29.670562+00:00","updated_at":"2026-04-19T04:31:29.670562+00:00"},{"id":447,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"1e86b777e61cf4eefc7d92fa57fa19dcc676013b","bug_id":"osv:PYSEC-2023-250","title":"PYSEC-2023-250: advisory","description":"aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Improper validation made it possible for an attacker to modify the HTTP request (e.g. to insert a new header) or create a new HTTP request if the attacker controls the HTTP version. The vulnerability only occurs if the attacker can control the HTTP version of the request. This issue has been patched in version 3.9.0.","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-q3qx-c6g2-7pw2","labels":["CVE-2023-49081","GHSA-q3qx-c6g2-7pw2"],"created_at":"2026-04-19T04:31:29.669863+00:00","updated_at":"2026-04-19T04:31:29.669863+00:00"},{"id":446,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"f016f0680e4ace6742b03a70cb0382ce86abe371","bug_id":"osv:PYSEC-2023-247","title":"PYSEC-2023-247: advisory","description":"aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Affected versions of aiohttp have a security vulnerability regarding the inconsistent interpretation of the http protocol. HTTP/1.1 is a persistent protocol, if both Content-Length(CL) and Transfer-Encoding(TE) header values are present it can lead to incorrect interpretation of two entities that parse the HTTP and we can poison other sockets with this incorrect interpretation. A possible Proof-of-Concept (POC) would be a configuration with a reverse proxy(frontend) that accepts both CL and TE headers and aiohttp as backend. As aiohttp parses anything with chunked, we can pass a chunked123 as TE, the frontend entity will ignore this header and will parse Content-Length. The impact of this vulnerability is that it is possible to bypass any proxy rule, poisoning sockets to other users like passing Authentication Headers, also if it is present an Open Redirect an attacker could combine it to redirect random users to another website and log the request. This vulnerability has been addressed in release 3.8.0 of aiohttp. Users are advised to upgrade. There are no known workarounds for this vulnerability.","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-xx9p-xxvh-7g8j","labels":["CVE-2023-47641","GHSA-xx9p-xxvh-7g8j"],"created_at":"2026-04-19T04:31:29.669019+00:00","updated_at":"2026-04-19T04:31:29.669019+00:00"},{"id":445,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"d5c12ba890557a575c313bb3017910d7616fce3d","bug_id":"osv:PYSEC-2023-246","title":"PYSEC-2023-246: advisory","description":"aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. The HTTP parser in AIOHTTP has numerous problems with header parsing, which could lead to request smuggling. This parser is only used when AIOHTTP_NO_EXTENSIONS is enabled (or not using a prebuilt wheel). These bugs have been addressed in commit `d5c12ba89` which has been included in release version 3.8.6. Users are advised to upgrade. There are no known workarounds for these issues.","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-gfw2-4jvh-wgfg","labels":["CVE-2023-47627","GHSA-gfw2-4jvh-wgfg"],"created_at":"2026-04-19T04:31:29.668223+00:00","updated_at":"2026-04-19T04:31:29.668223+00:00"},{"id":444,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.8.5","bug_id":"osv:PYSEC-2023-120","title":"aiohttp.web.Application vulnerable to HTTP request smuggling via llhttp HTTP request parser","description":"### Impact\n\naiohttp v3.8.4 and earlier are [bundled with llhttp v6.0.6](https://github.com/aio-libs/aiohttp/blob/v3.8.4/.gitmodules) which is vulnerable to CVE-2023-30589. The vulnerable code is used by aiohttp for its HTTP request parser when available which is the default case when installing from a wheel.\n\nThis vulnerability only affects users of aiohttp as an HTTP server (ie `aiohttp.Application`), you are not affected by this vulnerability if you are using aiohttp as an HTTP client library (ie `aiohttp.ClientSession`).\n\n### Reproducer\n\n```python\nfrom aiohttp import web\n\nasync def example(request: web.Request):\n    headers = dict(request.headers)\n    body = await request.content.read()\n    return web.Response(text=f\"headers: {headers} body: {body}\")\n\napp = web.Application()\napp.add_routes([web.post('/', example)])\nweb.run_app(app)\n```\n\nSending a crafted HTTP request will cause the server to misinterpret one of the HTTP header values leading to HTTP request smuggling.\n\n```console\n$ printf \"POST / HTTP/1.1\\r\\nHost: localhost:8080\\r\\nX-Abc: \\rxTransfer-Encoding: chunked\\r\\n\\r\\n1\\r\\nA\\r\\n0\\r\\n\\r\\n\" \\\n  | nc localhost 8080\n\nExpected output:\n  headers: {'Host': 'localhost:8080', 'X-Abc': '\\rxTransfer-Encoding: chunked'} body: b''\n\nActual output (note that 'Transfer-Encoding: chunked' is an HTTP header now and body is treated differently)\n  headers: {'Host': 'localhost:8080', 'X-Abc': '', 'Transfer-Encoding': 'chunked'} body: b'A'\n```\n\n### Patches\n\nUpgrade to the latest version of aiohttp to resolve this vulnerability. It has been fixed in v3.8.5: [`pip install aiohttp >= 3.8.5`](https://pypi.org/project/aiohttp/3.8.5/)\n\n### Workarounds\n\nIf you aren't able to upgrade you can reinstall aiohttp using `AIOHTTP_NO_EXTENSIONS=1` as an environment variable to disable the llhttp HTTP request parser implementation. The pure Python implementation isn't vulnerable to request smuggling:\n\n```console\n$ python -m pip uninstall --yes aiohttp\n$ AIOHTTP_NO_EXTENSIONS=1 python -m pip install --no-binary=aiohttp --no-cache aiohttp\n```\n\n### References\n\n* https://nvd.nist.gov/vuln/detail/CVE-2023-30589\n* https://hackerone.com/reports/2001873\n","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-45c4-8wx5-qw6w","labels":["CVE-2023-37276","GHSA-45c4-8wx5-qw6w"],"created_at":"2026-04-19T04:31:29.667238+00:00","updated_at":"2026-04-19T04:31:29.667238+00:00"},{"id":443,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"2545222a3853e31ace15d87ae0e2effb7da0c96b","bug_id":"osv:PYSEC-2021-76","title":"PYSEC-2021-76: advisory","description":"aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. In aiohttp before version 3.7.4 there is an open redirect vulnerability. A maliciously crafted link to an aiohttp-based web-server could redirect the browser to a different website. It is caused by a bug in the `aiohttp.web_middlewares.normalize_path_middleware` middleware. This security problem has been fixed in 3.7.4. Upgrade your dependency using pip as follows \"pip install aiohttp >= 3.7.4\". If upgrading is not an option for you, a workaround can be to avoid using `aiohttp.web_middlewares.normalize_path_middleware` in your applications.","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/commit/2545222a3853e31ace15d87ae0e2effb7da0c96b","labels":["CVE-2021-21330","GHSA-v6wp-4m6f-gcjg"],"created_at":"2026-04-19T04:31:29.665819+00:00","updated_at":"2026-04-19T04:31:29.665819+00:00"},{"id":441,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-w2fm-2cpv-w7v5","title":"aiohttp allows unlimited trailer headers, leading to possible uncapped memory usage","description":"### Summary\n\nInsufficient restrictions in header/trailer handling could cause uncapped memory usage.\n\n### Impact\n\nAn application could cause memory exhaustion when receiving an attacker controlled request or response. A vulnerable web application could mitigate these risks with a typical reverse proxy configuration.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/0c2e9da51126238a421568eb7c5b53e5b5d17b36","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-w2fm-2cpv-w7v5","labels":["CVE-2026-22815"],"created_at":"2026-04-19T04:31:29.663208+00:00","updated_at":"2026-04-19T04:31:29.663208+00:00"},{"id":439,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.9.0","bug_id":"osv:GHSA-qvrw-v9rv-5rjx","title":"aiohttp's ClientSession is vulnerable to CRLF injection via method","description":"### Summary\nImproper validation makes it possible for an attacker to modify the HTTP request (e.g. insert a new header) or even create a new HTTP request if the attacker controls the HTTP method.\n\n### Details\nThe vulnerability occurs only if the attacker can control the HTTP method (GET, POST etc.) of the request.\n\nPrevious releases performed no validation on the provided value. If an attacker controls the HTTP method it will be used as is and can lead to HTTP request smuggling.\n\n### PoC\nA minimal example can be found here:\nhttps://gist.github.com/jnovikov/7f411ae9fe6a9a7804cf162a3bdbb44b\n\n### Impact\nIf the attacker can control the HTTP version of the request it will be able to modify the request (request smuggling).\n\n### Workaround\nIf unable to upgrade and using user-provided values for the request method, perform manual validation of the user value (e.g. by restricting it to a few known values like GET, POST etc.).\n\nPatch: https://github.com/aio-libs/aiohttp/pull/7806/files","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-qvrw-v9rv-5rjx","labels":["CVE-2023-49082","PYSEC-2023-251"],"created_at":"2026-04-19T04:31:29.660474+00:00","updated_at":"2026-04-19T04:31:29.660474+00:00"},{"id":438,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.9.0","bug_id":"osv:GHSA-q3qx-c6g2-7pw2","title":"aiohttp's ClientSession is vulnerable to CRLF injection via version","description":"### Summary\nImproper validation make it possible for an attacker to modify the HTTP request (e.g. to insert a new header) or even create a new HTTP request if the attacker controls the HTTP version.\n\n### Details\nThe vulnerability only occurs if the attacker can control the HTTP version of the request (including its type).\nFor example if an unvalidated JSON value is used as a version and the attacker is then able to pass an array as the `version` parameter.\nFurthermore, the vulnerability only occurs when the `Connection` header is passed to the `headers` parameter.\n\nAt this point, the library will use the parsed value to create the request. If a list is passed, then it bypasses validation and it is possible to perform CRLF injection.\n\n### PoC\nThe POC below shows an example of providing an unvalidated array as a version:\nhttps://gist.github.com/jnovikov/184afb593d9c2114d77f508e0ccd508e\n\n### Impact\nCRLF injection leading to Request Smuggling.\n\n### Workaround\nIf these specific conditions are met and you are unable to upgrade, then validate the user input to the `version` parameter to ensure it is a `str`.\n\nPatch: https://github.com/aio-libs/aiohttp/pull/7835/files","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-q3qx-c6g2-7pw2","labels":["CVE-2023-49081","PYSEC-2023-250"],"created_at":"2026-04-19T04:31:29.659607+00:00","updated_at":"2026-04-19T04:31:29.659607+00:00"},{"id":437,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.8.6","bug_id":"osv:GHSA-pjjw-qhg8-p2p9","title":"aiohttp has vulnerable dependency that is vulnerable to request smuggling","description":"### Summary\nllhttp 8.1.1 is vulnerable to two request smuggling vulnerabilities.\nDetails have not been disclosed yet, so refer to llhttp for future information.\nThe issue is resolved by using llhttp 9+ (which is included in aiohttp 3.8.6+).","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-pjjw-qhg8-p2p9","labels":[],"created_at":"2026-04-19T04:31:29.658802+00:00","updated_at":"2026-04-19T04:31:29.658802+00:00"},{"id":436,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-p998-jp59-783m","title":"AIOHTTP affected by UNC SSRF/NTLMv2 Credential Theft/Local File Read in static resource handler on Windows","description":"### Summary\n\nOn Windows the static resource handler may expose information about a NTLMv2 remote path.\n\n### Impact\n\nIf an application is running on Windows, and using aiohttp's static resource handler (not recommended in production), then it may be possible for an attacker to extract the hash from an NTLMv2 path and then extract the user's credentials from there.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/0ae2aa076c84573df83fc1fdc39eec0f5862fe3d","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-p998-jp59-783m","labels":["CVE-2026-34515"],"created_at":"2026-04-19T04:31:29.657893+00:00","updated_at":"2026-04-19T04:31:29.657893+00:00"},{"id":433,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-m5qp-6w8w-w647","title":"AIOHTTP has a Multipart Header Size Bypass","description":"### Summary\n\nA response with an excessive number of multipart headers may be allowed to use more memory than intended, potentially allowing a DoS vulnerability.\n\n### Impact\n\nMultipart headers were not subject to the same size restrictions in place for normal headers, potentially allowing substantially more data to be loaded into memory than intended. However, other restrictions in place limit the impact of this vulnerability.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/8a74257b3804c9aac0bf644af93070f68f6c5a6f","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-m5qp-6w8w-w647","labels":["CVE-2026-34516"],"created_at":"2026-04-19T04:31:29.654718+00:00","updated_at":"2026-04-19T04:31:29.654718+00:00"},{"id":432,"ecosystem":"pypi","package_name":"aiohttp","affected_version":"3.10.0b1","fixed_version":"3.10.2","bug_id":"osv:GHSA-jwhx-xcg6-8xhj","title":"In aiohttp, compressed files as symlinks are not protected from path traversal","description":"### Summary\nStatic routes which contain files with compressed variants (`.gz` or `.br` extension) were vulnerable to path traversal outside the root directory if those variants are symbolic links.\n\n### Details\nThe server protects static routes from path traversal outside the root directory when `follow_symlinks=False` (default).  It does this by resolving the requested URL to an absolute path and then checking that path relative to the root.  However, these checks are not performed when looking for compressed variants in the `FileResponse` class, and symbolic links are then automatically followed when performing `Path.stat()` and `Path.open()` to send the file.\n\n### Impact\nServers with static routes that contain compressed variants as symbolic links, pointing outside the root directory, or that permit users to upload or create such links, are impacted.\n\n----\n\nPatch: https://github.com/aio-libs/aiohttp/pull/8653/files","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jwhx-xcg6-8xhj","labels":["CVE-2024-42367"],"created_at":"2026-04-19T04:31:29.653658+00:00","updated_at":"2026-04-19T04:31:29.653658+00:00"},{"id":431,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.3","bug_id":"osv:GHSA-jj3x-wxrx-4x23","title":"AIOHTTP vulnerable to DoS when bypassing asserts","description":"### Summary\nWhen assert statements are bypassed, an infinite loop can occur, resulting in a DoS attack when processing a POST body.\n\n### Impact\nIf optimisations are enabled (`-O` or `PYTHONOPTIMIZE=1`), and the application includes a handler that uses the `Request.post()` method, then an attacker may be able to execute a DoS attack with a specially crafted message.\n\n------\n\nPatch: https://github.com/aio-libs/aiohttp/commit/bc1319ec3cbff9438a758951a30907b072561259","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jj3x-wxrx-4x23","labels":["CVE-2025-69227"],"created_at":"2026-04-19T04:31:29.651553+00:00","updated_at":"2026-04-19T04:31:29.651553+00:00"},{"id":429,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.8.6","bug_id":"osv:GHSA-gfw2-4jvh-wgfg","title":"AIOHTTP has problems in HTTP parser (the python one, not llhttp)","description":"# Summary\nThe HTTP parser in AIOHTTP has numerous problems with header parsing, which could lead to request smuggling.\nThis parser is only used when `AIOHTTP_NO_EXTENSIONS` is enabled (or not using a prebuilt wheel).\n \n# Details\n\n## Bug 1: Bad parsing of `Content-Length` values\n\n### Description\nRFC 9110 says this:\n> `Content-Length = 1*DIGIT`\n\nAIOHTTP does not enforce this rule, presumably because of an incorrect usage of the builtin `int` constructor. Because the `int` constructor accepts `+` and `-` prefixes, and digit-separating underscores, using `int` to parse CL values leads AIOHTTP to significant misinterpretation.\n\n### Examples\n```\nGET / HTTP/1.1\\r\\n\nContent-Length: -0\\r\\n\n\\r\\n\nX\n```\n```\nGET / HTTP/1.1\\r\\n\nContent-Length: +0_1\\r\\n\n\\r\\n\nX\n```\n\n### Suggested action\nVerify that a `Content-Length` value consists only of ASCII digits before parsing, as the standard requires.\n\n## Bug 2: Improper handling of NUL, CR, and LF in header values\n\n### Description\nRFC 9110 says this:\n> Field values containing CR, LF, or NUL characters are invalid and dangerous, due to the varying ways that implementations might parse and interpret those characters; a recipient of CR, LF, or NUL within a field value MUST either reject the message or replace each of those characters with SP before further processing or forwarding of that message.\n\nAIOHTTP's HTTP parser does not enforce this rule, and will happily process header values containing these three forbidden characters without replacing them with SP.\n### Examples\n```\nGET / HTTP/1.1\\r\\n\nHeader: v\\x00alue\\r\\n\n\\r\\n\n```\n```\nGET / HTTP/1.1\\r\\n\nHeader: v\\ralue\\r\\n\n\\r\\n\n```\n```\nGET / HTTP/1.1\\r\\n\nHeader: v\\nalue\\r\\n\n\\r\\n\n```\n### Suggested action\nReject all messages with NUL, CR, or LF in a header value. The translation to space thing, while technically allowed, does not seem like a good idea to me.\n\n## Bug 3: Improper stripping of whitespace before colon in HTTP headers\n\n### Description\nRFC 9112 says this:\n> No whitespace is allowed between the field name and colon. In the past, differences in the handling of such whitespace have led to security vulnerabilities in request routing and response handling. A server MUST reject, with a response status code of 400 (Bad Request), any received request message that contains whitespace between a header field name and colon.\n\nAIOHTTP does not enforce this rule, and will simply strip any whitespace before the colon in an HTTP header.\n\n### Example\n```\nGET / HTTP/1.1\\r\\n\nContent-Length : 1\\r\\n\n\\r\\n\nX\n```\n\n### Suggested action\nReject all messages with whitespace before a colon in a header field, as the standard requires.\n\n# PoC\nExample requests are embedded in the previous section. To reproduce these bugs, start an AIOHTTP server without llhttp (i.e. `AIOHTTP_NO_EXTENSIONS=1`) and send the requests given in the previous section. (e.g. by `printf`ing into `nc`)\n\n# Impact\nEach of these bugs can be used for request smuggling.","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-gfw2-4jvh-wgfg","labels":["CVE-2023-47627","PYSEC-2023-246"],"created_at":"2026-04-19T04:31:29.647446+00:00","updated_at":"2026-04-19T04:31:29.647446+00:00"},{"id":428,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.3","bug_id":"osv:GHSA-g84x-mcqj-x9qq","title":"AIOHTTP vulnerable to DoS through chunked messages","description":"### Summary\n\nHandling of chunked messages can result in excessive blocking CPU usage when receiving a large number of chunks.\n\n### Impact\n\nIf an application makes use of the `request.read()` method in an endpoint, it may be possible for an attacker to cause the server to spend a moderate amount of blocking CPU time (e.g. 1 second) while processing the request. This could potentially lead to DoS as the server would be unable to handle other requests during that time.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/dc3170b56904bdf814228fae70a5501a42a6c712\nPatch: https://github.com/aio-libs/aiohttp/commit/4ed97a4e46eaf61bd0f05063245f613469700229","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-g84x-mcqj-x9qq","labels":["CVE-2025-69229"],"created_at":"2026-04-19T04:31:29.643344+00:00","updated_at":"2026-04-19T04:31:29.643344+00:00"},{"id":426,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-c427-h43c-vf67","title":"AIOHTTP accepts duplicate Host headers","description":"### Summary\n\nMultiple Host headers were allowed in aiohttp.\n\n### Impact\n\nMostly this doesn't affect aiohttp security itself, but if a reverse proxy is applying security rules depending on the target Host, it is theoretically possible that the proxy and aiohttp could process different host names, possibly resulting in bypassing a security check on the proxy and getting a request processed by aiohttp in a privileged sub app when using `Application.add_domain()`.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/e00ca3cca92c465c7913c4beb763a72da9ed8349\nPatch: https://github.com/aio-libs/aiohttp/commit/53e2e6fc58b89c6185be7820bd2c9f40216b3000","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-c427-h43c-vf67","labels":["CVE-2026-34525"],"created_at":"2026-04-19T04:31:29.640309+00:00","updated_at":"2026-04-19T04:31:29.640309+00:00"},{"id":423,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.9.2","bug_id":"osv:GHSA-8qpw-xqxj-h4r2","title":"aiohttp's HTTP parser (the python one, not llhttp) still overly lenient about separators","description":"### Summary\nSecurity-sensitive parts of the *Python HTTP parser* retained minor differences in allowable character sets, that must trigger error handling to robustly match frame boundaries of proxies in order to protect against injection of additional requests. Additionally, validation could trigger exceptions that were not handled consistently with processing of other malformed input.\n\n### Details\nThese problems are rooted in pattern matching protocol elements, previously improved by PR #3235 and GHSA-gfw2-4jvh-wgfg:\n\n1. The expression `HTTP/(\\d).(\\d)` lacked another backslash to clarify that the separator should be a literal dot, not just *any* Unicode code point (result: `HTTP/(\\d)\\.(\\d)`).\n\n2. The HTTP version was permitting Unicode digits, where only ASCII digits are standards-compliant.\n\n3. Distinct regular expressions for validating HTTP Method and Header field names were used - though both should (at least) apply the common restrictions of rfc9110 `token`.\n\n### PoC\n`GET / HTTP/1ö1`\n`GET / HTTP/1.𝟙`\n`GET/: HTTP/1.1`\n`Content-Encoding?: chunked`\n\n### Impact\nPrimarily concerns running an aiohttp server without llhttp:\n 1. **behind a proxy**: Being more lenient than internet standards require could, depending on deployment environment, assist in request smuggling.\n 2. **directly accessible** or exposed behind proxies relaying malformed input: the unhandled exception could cause excessive resource consumption on the application server and/or its logging facilities.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/pull/8074/files","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-8qpw-xqxj-h4r2","labels":["CVE-2024-23829","PYSEC-2024-26"],"created_at":"2026-04-19T04:31:29.637394+00:00","updated_at":"2026-04-19T04:31:29.637394+00:00"},{"id":422,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.10.11","bug_id":"osv:GHSA-8495-4g3g-x7pr","title":"aiohttp allows request smuggling due to incorrect parsing of chunk extensions","description":"### Summary\nThe Python parser parses newlines in chunk extensions incorrectly which can lead to request smuggling vulnerabilities under certain conditions.\n\n### Impact\nIf a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or `AIOHTTP_NO_EXTENSIONS` is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/259edc369075de63e6f3a4eaade058c62af0df71","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-8495-4g3g-x7pr","labels":["CVE-2024-52304"],"created_at":"2026-04-19T04:31:29.636594+00:00","updated_at":"2026-04-19T04:31:29.636594+00:00"},{"id":421,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.9.4","bug_id":"osv:GHSA-7gpw-8wmc-pm8g","title":"aiohttp Cross-site Scripting vulnerability on index pages for static file handling","description":"### Summary\n\nA XSS vulnerability exists on index pages for static file handling.\n\n### Details\n\nWhen using `web.static(..., show_index=True)`, the resulting index pages do not escape file names.\n\nIf users can upload files with arbitrary filenames to the static directory, the server is vulnerable to XSS attacks.\n\n### Workaround\n\nWe have always recommended using a reverse proxy server (e.g. nginx) for serving static files. Users following the recommendation are unaffected.\n\nOther users can disable `show_index` if unable to upgrade.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/pull/8319/files","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-7gpw-8wmc-pm8g","labels":["CVE-2024-27306"],"created_at":"2026-04-19T04:31:29.635845+00:00","updated_at":"2026-04-19T04:31:29.635845+00:00"},{"id":419,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.3","bug_id":"osv:GHSA-6jhg-hg63-jvvf","title":"AIOHTTP vulnerable to  denial of service through large payloads","description":"### Summary\nA request can be crafted in such a way that an aiohttp server's memory fills up uncontrollably during processing.\n\n### Impact\nIf an application includes a handler that uses the `Request.post()` method, an attacker may be able to freeze the server by exhausting the memory.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/b7dbd35375aedbcd712cbae8ad513d56d11cce60","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-6jhg-hg63-jvvf","labels":["CVE-2025-69228"],"created_at":"2026-04-19T04:31:29.633322+00:00","updated_at":"2026-04-19T04:31:29.633322+00:00"},{"id":413,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.8.5","bug_id":"osv:GHSA-45c4-8wx5-qw6w","title":"aiohttp.web.Application vulnerable to HTTP request smuggling via llhttp HTTP request parser","description":"### Impact\n\naiohttp v3.8.4 and earlier are [bundled with llhttp v6.0.6](https://github.com/aio-libs/aiohttp/blob/v3.8.4/.gitmodules) which is vulnerable to CVE-2023-30589. The vulnerable code is used by aiohttp for its HTTP request parser when available which is the default case when installing from a wheel.\n\nThis vulnerability only affects users of aiohttp as an HTTP server (ie `aiohttp.Application`), you are not affected by this vulnerability if you are using aiohttp as an HTTP client library (ie `aiohttp.ClientSession`).\n\n### Reproducer\n\n```python\nfrom aiohttp import web\n\nasync def example(request: web.Request):\n    headers = dict(request.headers)\n    body = await request.content.read()\n    return web.Response(text=f\"headers: {headers} body: {body}\")\n\napp = web.Application()\napp.add_routes([web.post('/', example)])\nweb.run_app(app)\n```\n\nSending a crafted HTTP request will cause the server to misinterpret one of the HTTP header values leading to HTTP request smuggling.\n\n```console\n$ printf \"POST / HTTP/1.1\\r\\nHost: localhost:8080\\r\\nX-Abc: \\rxTransfer-Encoding: chunked\\r\\n\\r\\n1\\r\\nA\\r\\n0\\r\\n\\r\\n\" \\\n  | nc localhost 8080\n\nExpected output:\n  headers: {'Host': 'localhost:8080', 'X-Abc': '\\rxTransfer-Encoding: chunked'} body: b''\n\nActual output (note that 'Transfer-Encoding: chunked' is an HTTP header now and body is treated differently)\n  headers: {'Host': 'localhost:8080', 'X-Abc': '', 'Transfer-Encoding': 'chunked'} body: b'A'\n```\n\n### Patches\n\nUpgrade to the latest version of aiohttp to resolve this vulnerability. It has been fixed in v3.8.5: [`pip install aiohttp >= 3.8.5`](https://pypi.org/project/aiohttp/3.8.5/)\n\n### Workarounds\n\nIf you aren't able to upgrade you can reinstall aiohttp using `AIOHTTP_NO_EXTENSIONS=1` as an environment variable to disable the llhttp HTTP request parser implementation. The pure Python implementation isn't vulnerable to request smuggling:\n\n```console\n$ python -m pip uninstall --yes aiohttp\n$ AIOHTTP_NO_EXTENSIONS=1 python -m pip install --no-binary=aiohttp --no-cache aiohttp\n```\n\n### References\n\n* https://nvd.nist.gov/vuln/detail/CVE-2023-30589\n* https://hackerone.com/reports/2001873\n","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-45c4-8wx5-qw6w","labels":["CVE-2023-37276","PYSEC-2023-120"],"created_at":"2026-04-19T04:31:29.626561+00:00","updated_at":"2026-04-19T04:31:29.626561+00:00"},{"id":410,"ecosystem":"pypi","package_name":"aiohttp","affected_version":"3.10.6","fixed_version":"3.10.11","bug_id":"osv:GHSA-27mf-ghqm-j3j8","title":"aiohttp has a memory leak when middleware is enabled when requesting a resource with a non-allowed method","description":"### Summary\n\nA memory leak can occur when a request produces a `MatchInfoError`. This was caused by adding an entry to a cache on each request, due to the building of each `MatchInfoError` producing a unique cache entry.\n\n### Impact\n\nIf the user is making use of any middlewares with `aiohttp.web` then it is advisable to upgrade immediately.\n\nAn attacker may be able to exhaust the memory resources of a server by sending a substantial number (100,000s to millions) of such requests.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/bc15db61615079d1b6327ba42c682f758fa96936","severity":"medium","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-27mf-ghqm-j3j8","labels":["CVE-2024-52303"],"created_at":"2026-04-19T04:31:29.621652+00:00","updated_at":"2026-04-19T04:31:29.621652+00:00"},{"id":442,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.8.0","bug_id":"osv:GHSA-xx9p-xxvh-7g8j","title":"Aiohttp has inconsistent interpretation of `Content-Length` vs. `Transfer-Encoding` differing in C and Python fallbacks","description":"### Impact\n\nAiohttp has a security vulnerability regarding the inconsistent interpretation of the http protocol. As we know that HTTP/1.1 is persistent, if we have both Content-Length(CL) and Transfer-Encoding(TE) it can lead to incorrect interpretation of two entities that parse the HTTP and we can poison other sockets with this incorrect interpretation.\n\nA possible Proof-of-Concept (POC) would be a configuration with a reverse proxy(frontend) that accepts both CL and TE headers and aiohttp as backend. As aiohttp parses anything with chunked, we can pass a chunked123 as TE, the frontend entity will ignore this header and will parse Content-Length. I can give a Dockerfile with the configuration if you want.\n\nThe impact of this vulnerability is that it is possible to bypass any proxy rule, poisoning sockets to other users like passing Authentication Headers, also if it is present an Open Redirect (just like CVE-2021-21330) we can combine it to redirect random users to our website and log the request.\n\n\n### References\n\n- https://github.com/aio-libs/aiohttp/commit/f016f0680e4ace6742b03a70cb0382ce86abe371","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-xx9p-xxvh-7g8j","labels":["CVE-2023-47641","PYSEC-2023-247"],"created_at":"2026-04-19T04:31:29.664164+00:00","updated_at":"2026-04-19T04:31:29.664164+00:00"},{"id":440,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.7.4","bug_id":"osv:GHSA-v6wp-4m6f-gcjg","title":"`aiohttp` Open Redirect vulnerability (`normalize_path_middleware` middleware)","description":"### Impact\n\nOpen redirect vulnerability — a maliciously crafted link to an aiohttp-based web-server could redirect the browser to a different website.\n\nIt is caused by a bug in the `aiohttp.web_middlewares.normalize_path_middleware` middleware.\n\n### Patches\n\nThis security problem has been fixed in v3.7.4. Upgrade your dependency as follows:\n[`pip install aiohttp >= 3.7.4`]\n\n### Workarounds\n\nIf upgrading is not an option for you, a workaround can be to avoid using `aiohttp.web_middlewares.normalize_path_middleware` in your applications.\n\n### References\n\n* [aiohttp @ PyPI]\n* [GHSA-v6wp-4m6f-gcjg]\n* [OWASP page on open redirects]\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in the [aiohttp repo](https://github.com/aio-libs/aiohttp/issues/new/choose)\n* Email us at wk+aio-libs-security@sydorenko.org.ua and/or andrew.svetlov+aio-libs-security@gmail.com\n\nCredit: [Jelmer Vernooij] and [Beast Glatisant].\n\n[aiohttp @ PyPI]: https://pypi.org/p/aiohttp\n[`pip install aiohttp >= 3.7.4`]: https://pypi.org/project/aiohttp/3.7.4/\n[GHSA-v6wp-4m6f-gcjg]: https://github.com/aio-libs/aiohttp/security/advisories/GHSA-v6wp-4m6f-gcjg\n[OWASP page on open redirects]:\nhttps://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html\n\n[Jelmer Vernooij]: https://jelmer.uk\n[Beast Glatisant]: https://github.com/g147","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-v6wp-4m6f-gcjg","labels":["CVE-2021-21330","PYSEC-2021-76"],"created_at":"2026-04-19T04:31:29.661590+00:00","updated_at":"2026-04-19T04:31:29.661590+00:00"},{"id":435,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-mwh4-6h8g-pg8w","title":"AIOHTTP has HTTP response splitting via \\r in reason phrase","description":"### Summary\n\nAn attacker who controls the `reason` parameter when creating a `Response` may be able to inject extra headers or similar exploits.\n\n### Impact\n\nIn the unlikely situation that an application allows untrusted data to be used in the response's `reason` parameter, then an attacker could manipulate the response to send something different from what the developer intended.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/53b35a2f8869c37a133e60bf1a82a1c01642ba2b","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-mwh4-6h8g-pg8w","labels":["CVE-2026-34519"],"created_at":"2026-04-19T04:31:29.656721+00:00","updated_at":"2026-04-19T04:31:29.656721+00:00"},{"id":434,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.3","bug_id":"osv:GHSA-mqqc-3gqh-h2x8","title":"AIOHTTP has unicode match groups in regexes for ASCII protocol elements","description":"### Summary\n\nThe parser allows non-ASCII decimals to be present in the Range header.\n\n### Impact\n\nThere is no known impact, but there is the possibility that there's a method to exploit a request smuggling vulnerability.\n\n----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/c7b7a044f88c71cefda95ec75cdcfaa4792b3b96","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-mqqc-3gqh-h2x8","labels":["CVE-2025-69225"],"created_at":"2026-04-19T04:31:29.655629+00:00","updated_at":"2026-04-19T04:31:29.655629+00:00"},{"id":430,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-hcc4-c3v8-rx92","title":"AIOHTTP Affected by Denial of Service (DoS) via Unbounded DNS Cache in TCPConnector","description":"### Summary\n\nAn unbounded DNS cache could result in excessive memory usage possibly resulting in a DoS situation.\n\n### Impact\n\nIf an application makes requests to a very large number of hosts, this could cause the DNS cache to continue growing and slowly use excessive amounts of memory.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/c4d77c3533122be353b8afca8e8675e3b4cbda98","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-hcc4-c3v8-rx92","labels":["CVE-2026-34513"],"created_at":"2026-04-19T04:31:29.649116+00:00","updated_at":"2026-04-19T04:31:29.649116+00:00"},{"id":427,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.3","bug_id":"osv:GHSA-fh55-r93g-j68g","title":"AIOHTTP Vulnerable to Cookie Parser Warning Storm","description":"### Summary\nReading multiple invalid cookies can lead to a logging storm.\n\n### Impact\nIf the ``cookies`` attribute is accessed in an application, then an attacker may be able to trigger a storm of warning-level logs using a specially crafted Cookie header.\n\n----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/64629a0834f94e46d9881f4e99c41a137e1f3326","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-fh55-r93g-j68g","labels":["CVE-2025-69230"],"created_at":"2026-04-19T04:31:29.642284+00:00","updated_at":"2026-04-19T04:31:29.642284+00:00"},{"id":425,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-966j-vmvw-g2g9","title":"AIOHTTP leaks Cookie and Proxy-Authorization headers on cross-origin redirect","description":"### Summary\n\nWhen following redirects to a different origin, aiohttp drops the Authorization header, but retains the Cookie and Proxy-Authorization headers.\n\n### Impact\n\nThe Cookie and Proxy-Authorizations headers could contain sensitive information which may be leaked to an unintended party after following a redirect.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/5351c980dcec7ad385730efdf4e1f4338b24fdb6","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-966j-vmvw-g2g9","labels":["CVE-2026-34518"],"created_at":"2026-04-19T04:31:29.639432+00:00","updated_at":"2026-04-19T04:31:29.639432+00:00"},{"id":424,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.12.14","bug_id":"osv:GHSA-9548-qrrj-x5pj","title":"AIOHTTP is vulnerable to HTTP Request/Response Smuggling through incorrect parsing of chunked trailer sections","description":"### Summary\nThe Python parser is vulnerable to a request smuggling vulnerability due to not parsing trailer sections of an HTTP request.\n\n### Impact\nIf a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or AIOHTTP_NO_EXTENSIONS is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections.\n\n----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/e8d774f635dc6d1cd3174d0e38891da5de0e2b6a","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-9548-qrrj-x5pj","labels":["CVE-2025-53643"],"created_at":"2026-04-19T04:31:29.638567+00:00","updated_at":"2026-04-19T04:31:29.638567+00:00"},{"id":418,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.3","bug_id":"osv:GHSA-69f9-5gxw-wvc2","title":"AIOHTTP's unicode processing of header values could cause parsing discrepancies","description":"### Summary\nThe Python HTTP parser may allow a request smuggling attack with the presence of non-ASCII characters.\n\n### Impact\nIf a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or AIOHTTP_NO_EXTENSIONS is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections.\n\n------\n\nPatch: https://github.com/aio-libs/aiohttp/commit/32677f2adfd907420c078dda6b79225c6f4ebce0","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-69f9-5gxw-wvc2","labels":["CVE-2025-69224"],"created_at":"2026-04-19T04:31:29.632540+00:00","updated_at":"2026-04-19T04:31:29.632540+00:00"},{"id":417,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-63hf-3vf5-4wqf","title":"AIOHTTP's C parser (llhttp) accepts null bytes and control characters in response header values - header injection/security bypass","description":"### Summary\n\nThe C parser (the default for most installs) accepted null bytes and control characters is response headers.\n\n### Impact\n\nAn attacker could send header values that are interpreted differently than expected due to the presence of control characters. For example, `request.url.origin()` may return a different value than the raw Host header, or what a reverse proxy interpreted it as., potentially resulting in some kind of security bypass.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/9370b9714a7a56003cacd31a9b4ae16eab109ba4","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-63hf-3vf5-4wqf","labels":["CVE-2026-34520"],"created_at":"2026-04-19T04:31:29.631664+00:00","updated_at":"2026-04-19T04:31:29.631664+00:00"},{"id":414,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.3","bug_id":"osv:GHSA-54jq-c3m8-4m76","title":"AIOHTTP vulnerable to brute-force leak of internal static file path components","description":"### Summary\nPath normalization for static files prevents path traversal, but opens up the ability for an attacker to ascertain the\nexistence of absolute path components.\n\n### Impact\nIf an application uses `web.static()` (not recommended for production deployments), it may be possible for an attacker to ascertain the existence of path components.\n\n------\n\nPatch: https://github.com/aio-libs/aiohttp/commit/f2a86fd5ac0383000d1715afddfa704413f0711e","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-54jq-c3m8-4m76","labels":["CVE-2025-69226"],"created_at":"2026-04-19T04:31:29.628981+00:00","updated_at":"2026-04-19T04:31:29.628981+00:00"},{"id":412,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-3wq7-rqq7-wx6j","title":"AIOHTTP has late size enforcement for non-file multipart fields causes memory DoS","description":"### Summary\n\nFor some multipart form fields, aiohttp read the entire field into memory before checking client_max_size.\n\n### Impact\n\nIf an application uses `Request.post()` an attacker can send a specially crafted multipart request to force significant temporary memory allocation even when the request is ultimately rejected.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/cbb774f38330563422ca0c413a71021d7b944145","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-3wq7-rqq7-wx6j","labels":["CVE-2026-34517"],"created_at":"2026-04-19T04:31:29.624896+00:00","updated_at":"2026-04-19T04:31:29.624896+00:00"},{"id":411,"ecosystem":"pypi","package_name":"aiohttp","affected_version":null,"fixed_version":"3.13.4","bug_id":"osv:GHSA-2vrm-gr82-f7m5","title":"AIOHTTP has CRLF injection through multipart part content type header construction","description":"### Summary\n\nAn attacker who controls the `content_type` parameter in aiohttp could use this to inject extra headers or similar exploits.\n\n### Impact\n\nIf an application allows untrusted data to be used for the multipart `content_type` parameter when constructing a request, an attacker may be able to manipulate the request to send something other than what the developer intended.\n\n-----\n\nPatch: https://github.com/aio-libs/aiohttp/commit/9a6ada97e2c6cf1ce31727c6c9fcea17c21f6f06","severity":"low","status":"fixed","source":"osv","source_url":"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-2vrm-gr82-f7m5","labels":["CVE-2026-34514"],"created_at":"2026-04-19T04:31:29.623811+00:00","updated_at":"2026-04-19T04:31:29.623811+00:00"}],"total":41,"_cache":"miss"}