https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 04:52:32 +0000 https://vulnerability.circl.lu/vuln/cve-2026-54275 <p><strong>Affected:</strong> aio-libs aiohttp</p> <p>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed when an existing connection is reused. If an application makes multiple requests to the same domain, but with different per-request server_hostname parameters, then the later calls may succeed by reusing the existing connection when they should have been rejected due to the TLS SNI check. This vulnerability is fixed in 3.14.1.</p> <p><strong>Affected:</strong> aio-libs aiohttp</p> <p>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed when an existing connection is reused. If an application makes multiple requests to the same domain, but with different per-request server_hostname parameters, then the later calls may succeed by reusing the existing connection when they should have been rejected due to the TLS SNI check. This vulnerability is fixed in 3.14.1.</p> https://vulnerability.circl.lu/vuln/cve-2026-54275 https://vulnerability.circl.lu/vuln/ghsa-4m7w-qmgq-4wj5 <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>### Summary</p> <p>The `server_hostname` TLS SNI check can be bypassed when an existing connection is reused.</p> <p>### Impact</p> <p>If an application makes multiple requests to the same domain, but with different per-request `server_hostname` parameters, then the later calls may succeed by reusing the existing connection when they should have been rejected due to the TLS SNI check.</p> <p>### Workaround</p> <p>Disable keep_alive if you need to change the `server_hostname` check between requests.</p> <p>-----</p> <p>Patch: https://github.com/aio-libs/aiohttp/commit/0ca2b6c28a25726527a8b60f25960262a91ed0e0</p> <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>### Summary</p> <p>The `server_hostname` TLS SNI check can be bypassed when an existing connection is reused.</p> <p>### Impact</p> <p>If an application makes multiple requests to the same domain, but with different per-request `server_hostname` parameters, then the later calls may succeed by reusing the existing connection when they should have been rejected due to the TLS SNI check.</p> <p>### Workaround</p> <p>Disable keep_alive if you need to change the `server_hostname` check between requests.</p> <p>-----</p> <p>Patch: https://github.com/aio-libs/aiohttp/commit/0ca2b6c28a25726527a8b60f25960262a91ed0e0</p> https://vulnerability.circl.lu/vuln/ghsa-4m7w-qmgq-4wj5 https://vulnerability.circl.lu/vuln/pysec-2026-237 <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed when an existing connection is reused. If an application makes multiple requests to the same domain, but with different per-request server_hostname parameters, then the later calls may succeed by reusing the existing connection when they should have been rejected due to the TLS SNI check. This vulnerability is fixed in 3.14.1.</p> <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed when an existing connection is reused. If an application makes multiple requests to the same domain, but with different per-request server_hostname parameters, then the later calls may succeed by reusing the existing connection when they should have been rejected due to the TLS SNI check. This vulnerability is fixed in 3.14.1.</p> https://vulnerability.circl.lu/vuln/pysec-2026-237