<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 16:25:27 +0000</lastBuildDate>
    <item>
      <title>BREW-aider-CVE-2026-54275 — aiohttp: TLS Server Hostname Override Is Ignored When Reusing HTTPS Connections</title>
      <link>https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-54275</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `server_hostname` TLS SNI check can be bypassed when an existing connection is reused.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;Disable keep_alive if you need to change the `server_hostname` check between requests.&lt;/p&gt;
&lt;p&gt;-----&lt;/p&gt;
&lt;p&gt;Patch: https://github.com/aio-libs/aiohttp/commit/0ca2b6c28a25726527a8b60f25960262a91ed0e0&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `server_hostname` TLS SNI check can be bypassed when an existing connection is reused.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;Disable keep_alive if you need to change the `server_hostname` check between requests.&lt;/p&gt;
&lt;p&gt;-----&lt;/p&gt;
&lt;p&gt;Patch: https://github.com/aio-libs/aiohttp/commit/0ca2b6c28a25726527a8b60f25960262a91ed0e0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-54275</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0933 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0933</link>
      <description>certfr-2026-avi-0933</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0933</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-MI51590 — Security fixes in kserve-storage-controller 0.19.0-r0</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-mi51590</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: kserve-storage-controller&lt;/p&gt;
&lt;p&gt;Package kserve-storage-controller version 0.19.0-r0 fixes 91 vulnerabilities: CVE-2024-12254, CVE-2024-12718, CVE-2024-6232, CVE-2024-7592, CVE-2024-9287...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: kserve-storage-controller&lt;/p&gt;
&lt;p&gt;Package kserve-storage-controller version 0.19.0-r0 fixes 91 vulnerabilities: CVE-2024-12254, CVE-2024-12718, CVE-2024-6232, CVE-2024-7592, CVE-2024-9287...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-mi51590</guid>
    </item>
    <item>
      <title>EUVD-2026-329047</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329047</link>
      <description>EUVD-2026-329047</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329047</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54275</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54275</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54275</guid>
    </item>
    <item>
      <title>GHSA-4m7w-qmgq-4wj5 — aiohttp: TLS Server Hostname Override Is Ignored When Reusing HTTPS Connections</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4m7w-qmgq-4wj5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: aiohttp&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `server_hostname` TLS SNI check can be bypassed when an existing connection is reused.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;Disable keep_alive if you need to change the `server_hostname` check between requests.&lt;/p&gt;
&lt;p&gt;-----&lt;/p&gt;
&lt;p&gt;Patch: https://github.com/aio-libs/aiohttp/commit/0ca2b6c28a25726527a8b60f25960262a91ed0e0&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: aiohttp&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `server_hostname` TLS SNI check can be bypassed when an existing connection is reused.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;Disable keep_alive if you need to change the `server_hostname` check between requests.&lt;/p&gt;
&lt;p&gt;-----&lt;/p&gt;
&lt;p&gt;Patch: https://github.com/aio-libs/aiohttp/commit/0ca2b6c28a25726527a8b60f25960262a91ed0e0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4m7w-qmgq-4wj5</guid>
    </item>
    <item>
      <title>OESA-2026-2838 — python-aiohttp security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2838</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: python-aiohttp&lt;/p&gt;
&lt;p&gt;Async http client/server framework (asyncio).&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;No limit was present on the number of pipelined requests that could be queued.  Impact An attacker may be able to use pipelined requests to use excessive amounts of memory, potentially leading to DoS.(CVE-2026-54273)&lt;/p&gt;
&lt;p&gt;If an attacker sends large incomplete websocket frame payloads, it may be possible to bypass the usual size limits on memory use.  Impact If a web application has WebSocket endpoints, it may be possible for an attacker to execute a DoS attack through excessive memory use(CVE-2026-54274)&lt;/p&gt;
&lt;p&gt;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.(CVE-2026-54275)&lt;/p&gt;
&lt;p&gt;If the client follows a redirect (the default option) to an attacker controlled domain, the attacker may be able to extract the auth digest.&#13;
&#13;
This likely requires an open redirect vulnerability or similar on the target domain for an attacker to be able to execute. Further, the attacker is only receiving the digest, so should only be able to extract the user&amp;amp;apos;s credentials if the cryptography is weak or there is some kind of password reuse.(CVE-2026-54276)&lt;/p&gt;
&lt;p&gt;It is possible to bypass the max_line_size check in parts of an HTTP request in the C parser. Impact If using the optimized C parser (the default in pre-built wheels), then an attacker ma…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: python-aiohttp&lt;/p&gt;
&lt;p&gt;Async http client/server framework (asyncio).&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;No limit was present on the number of pipelined requests that could be queued.  Impact An attacker may be able to use pipelined requests to use excessive amounts of memory, potentially leading to DoS.(CVE-2026-54273)&lt;/p&gt;
&lt;p&gt;If an attacker sends large incomplete websocket frame payloads, it may be possible to bypass the usual size limits on memory use.  Impact If a web application has WebSocket endpoints, it may be possible for an attacker to execute a DoS attack through excessive memory use(CVE-2026-54274)&lt;/p&gt;
&lt;p&gt;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.(CVE-2026-54275)&lt;/p&gt;
&lt;p&gt;If the client follows a redirect (the default option) to an attacker controlled domain, the attacker may be able to extract the auth digest.&#13;
&#13;
This likely requires an open redirect vulnerability or similar on the target domain for an attacker to be able to execute. Further, the attacker is only receiving the digest, so should only be able to extract the user&amp;amp;apos;s credentials if the cryptography is weak or there is some kind of password reuse.(CVE-2026-54276)&lt;/p&gt;
&lt;p&gt;It is possible to bypass the max_line_size check in parts of an HTTP request in the C parser. Impact If using the optimized C parser (the default in pre-built wheels), then an attacker ma…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2838</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11097-1 — python311-aiohttp-3.14.1-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11097-1</link>
      <description>&lt;p&gt;python311-aiohttp-3.14.1-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python311-aiohttp-3.14.1-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11097-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-237</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-237</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: aiohttp&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: aiohttp&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-237</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22819-1 — Security update for python-aiohttp</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22819-1</link>
      <description>&lt;p&gt;Security update for python-aiohttp&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for python-aiohttp&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:22819-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-54275</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54275</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: python-aiohttp, Ubuntu:Pro:18.04:LTS: python-aiohttp, Ubuntu:Pro:20.04:LTS: python-aiohttp, Ubuntu:Pro:22.04:LTS: python-aiohttp, Ubuntu:Pro:24.04:LTS: python-aiohttp, Ubuntu:25.10: python-aiohttp, Ubuntu:Pro:26.04:LTS: python-aiohttp&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: python-aiohttp, Ubuntu:Pro:18.04:LTS: python-aiohttp, Ubuntu:Pro:20.04:LTS: python-aiohttp, Ubuntu:Pro:22.04:LTS: python-aiohttp, Ubuntu:Pro:24.04:LTS: python-aiohttp, Ubuntu:25.10: python-aiohttp, Ubuntu:Pro:26.04:LTS: python-aiohttp&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54275</guid>
    </item>
  </channel>
</rss>
