https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-29T15:58:15.852594+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/cve-2026-54275 CVE-2026-54275 — AIOHTTP: TLS Server Hostname Override Is Ignored When Reusing HTTPS Connections 2026-09-29T15:58:17.678898+00:00

Affected: aio-libs aiohttp

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.

 https://vulnerability.circl.lu/vuln/ghsa-4m7w-qmgq-4wj5 GHSA-4m7w-qmgq-4wj5 — aiohttp: TLS Server Hostname Override Is Ignored When Reusing HTTPS Connections 2026-09-29T15:58:17.679032+00:00

Affected: PyPI: aiohttp

### Summary

The `server_hostname` TLS SNI check can be bypassed when an existing connection is reused.

### Impact

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.

### Workaround

Disable keep_alive if you need to change the `server_hostname` check between requests.

-----

Patch: https://github.com/aio-libs/aiohttp/commit/0ca2b6c28a25726527a8b60f25960262a91ed0e0

 https://vulnerability.circl.lu/vuln/pysec-2026-237 PYSEC-2026-237 2026-09-29T15:58:17.679103+00:00

Affected: PyPI: aiohttp

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.