<?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://vulnerability.circl.lu</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>Wed, 07 Oct 2026 23:54:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-23334 — aiohttp.web.static(follow_symlinks=True) is vulnerable to directory traversal</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-23334</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; aio-libs aiohttp&lt;/p&gt;
&lt;p&gt;aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option &amp;#39;follow_symlinks&amp;#39; can be used to determine whether to follow symbolic links outside the static root directory. When &amp;#39;follow_symlinks&amp;#39; is set to True, there is no validation to check if reading a file is within the root directory. This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present.  Disabling follow_symlinks and using a reverse proxy are encouraged mitigations.  Version 3.9.2 fixes this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; aio-libs aiohttp&lt;/p&gt;
&lt;p&gt;aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option &amp;#39;follow_symlinks&amp;#39; can be used to determine whether to follow symbolic links outside the static root directory. When &amp;#39;follow_symlinks&amp;#39; is set to True, there is no validation to check if reading a file is within the root directory. This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present.  Disabling follow_symlinks and using a reverse proxy are encouraged mitigations.  Version 3.9.2 fixes this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-23334</guid>
    </item>
    <item>
      <title>USN-6991-1 — python-aiohttp vulnerability</title>
      <link>https://vulnerability.circl.lu/vuln/usn-6991-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: python-aiohttp, Ubuntu:Pro:20.04:LTS: python-aiohttp, Ubuntu:22.04:LTS: python-aiohttp, Ubuntu:24.04:LTS: python-aiohttp&lt;/p&gt;
&lt;p&gt;It was discovered that AIOHTTP did not properly restrict file access when
the &amp;#39;follow_symlinks&amp;#39; option was set to True. A remote attacker could 
possibly use this issue to access unauthorized files on the system.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: python-aiohttp, Ubuntu:Pro:20.04:LTS: python-aiohttp, Ubuntu:22.04:LTS: python-aiohttp, Ubuntu:24.04:LTS: python-aiohttp&lt;/p&gt;
&lt;p&gt;It was discovered that AIOHTTP did not properly restrict file access when
the &amp;#39;follow_symlinks&amp;#39; option was set to True. A remote attacker could 
possibly use this issue to access unauthorized files on the system.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-6991-1</guid>
    </item>
  </channel>
</rss>
