Python aiohttp: Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed when an existing connection is reused. (CVE-2026-54275)
Description
Python aiohttp versions prior to 3.14.1 contain a vulnerability where the server_hostname TLS SNI check can be bypassed when an existing connection is reused. This allows later requests with different server_hostname parameters to reuse a TLS connection that should have been rejected. The issue is fixed in version 3.14.1.
CVSS v3.1
Score 7.5high
Affected software
pkg:deb/ubuntu/python-aiohttp?arch=source&distro=esm-apps-legacy/xenialpkg:deb/ubuntu/python-aiohttp?arch=source&distro=esm-apps/bionicpkg:deb/ubuntu/python-aiohttp?arch=source&distro=esm-apps/focalpkg:deb/ubuntu/python-aiohttp?arch=source&distro=esm-apps/jammypkg:deb/ubuntu/python-aiohttp?arch=source&distro=esm-apps/noblepkg:deb/ubuntu/python-aiohttp?arch=source&distro=questingpkg:deb/ubuntu/python-aiohttp?arch=source&distro=stonkingpkg:deb/ubuntu/python-aiohttp?arch=source&distro=esm-apps/resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The aiohttp asynchronous HTTP client/server framework for Python has a vulnerability (CVE-2026-54275) affecting versions prior to 3.14.1. When an application makes multiple requests to the same domain but with different per-request server_hostname parameters, the TLS Server Name Indication (SNI) check can be bypassed if an existing TLS connection is reused. This means that the later requests may succeed without proper TLS hostname verification, potentially undermining TLS security guarantees. The vulnerability is resolved in aiohttp version 3.14.1.
Potential Impact
This vulnerability can lead to improper TLS hostname verification when reusing connections, which may allow an attacker to bypass TLS SNI checks. While the CVSS score is 7.5 (medium severity) with no confidentiality or integrity impact, it has a high impact on availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade aiohttp to version 3.14.1 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-54275
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:Pro:18.04:LTS","Ubuntu:Pro:20.04:LTS","Ubuntu:Pro:22.04:LTS","Ubuntu:Pro:24.04:LTS","Ubuntu:25.10","Ubuntu:26.10","Ubuntu:Pro:26.04:LTS"]
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ad3f5fd2cdf04f656663fec
Added to database: 10/17/2026, 22:26:05 UTC
Last enriched: 10/18/2026, 00:49:40 UTC
Last updated: 10/18/2026, 00:49:40 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.