<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T22:57:33.292639+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2024-52303</id>
    <title>CVE-2024-52303 — aiohttp memory leak when middleware is enabled when requesting a resource with a non-allowed method</title>
    <updated>2026-09-28T22:57:34.280909+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> aio-libs aiohttp, aiohttp aio-libs</p>
<p>aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. In versions starting with 3.10.6 and prior to 3.10.11, a memory leak can occur when a request produces a MatchInfoError. This was caused by adding an entry to a cache on each request, due to the building of each MatchInfoError producing a unique cache entry. An attacker may be able to exhaust the memory resources of a server by sending a substantial number (100,000s to millions) of such requests. Those who use any middlewares with aiohttp.web should upgrade to version 3.10.11 to receive a patch.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-52303"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-27mf-ghqm-j3j8</id>
    <title>GHSA-27mf-ghqm-j3j8 — aiohttp has a memory leak when middleware is enabled when requesting a resource with a non-allowed method</title>
    <updated>2026-09-28T22:57:34.281179+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>A memory leak can occur when a request produces a `MatchInfoError`. This was caused by adding an entry to a cache on each request, due to the building of each `MatchInfoError` producing a unique cache entry.</p>
<p>### Impact</p>
<p>If the user is making use of any middlewares with `aiohttp.web` then it is advisable to upgrade immediately.</p>
<p>An attacker may be able to exhaust the memory resources of a server by sending a substantial number (100,000s to millions) of such requests.</p>
<p>-----</p>
<p>Patch: https://github.com/aio-libs/aiohttp/commit/bc15db61615079d1b6327ba42c682f758fa96936</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-27mf-ghqm-j3j8"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-1096</id>
    <title>PYSEC-2026-1096 — aiohttp has a memory leak when middleware is enabled when requesting a resource with a non-allowed method</title>
    <updated>2026-09-28T22:57:34.281242+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>A memory leak can occur when a request produces a `MatchInfoError`. This was caused by adding an entry to a cache on each request, due to the building of each `MatchInfoError` producing a unique cache entry.</p>
<p>### Impact</p>
<p>If the user is making use of any middlewares with `aiohttp.web` then it is advisable to upgrade immediately.</p>
<p>An attacker may be able to exhaust the memory resources of a server by sending a substantial number (100,000s to millions) of such requests.</p>
<p>-----</p>
<p>Patch: https://github.com/aio-libs/aiohttp/commit/bc15db61615079d1b6327ba42c682f758fa96936</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-1096"/>
  </entry>
</feed>
