<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-14T19:45:51.328651+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-4m7w-qmgq-4wj5</id>
    <title>GHSA-4m7w-qmgq-4wj5 — aiohttp: TLS Server Hostname Override Is Ignored When Reusing HTTPS Connections</title>
    <updated>2026-10-14T19:45:51.344824+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-4m7w-qmgq-4wj5"/>
  </entry>
</feed>
