<?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-10-04T18:34:57.847362+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-2025-69226</id>
    <title>CVE-2025-69226 — AIOHTTP allows for a brute-force leak of internal static ﬁlepath components</title>
    <updated>2026-10-04T18:34:57.854454+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> aio-libs aiohttp</p>
<p>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Versions 3.13.2 and below enable an attacker to ascertain the existence of absolute path components through the path normalization logic for static files meant to prevent path traversal. If an application uses web.static() (not recommended for production deployments), it may be possible for an attacker to ascertain the existence of path components. This issue is fixed in version 3.13.3.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-69226"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-54jq-c3m8-4m76</id>
    <title>GHSA-54jq-c3m8-4m76 — AIOHTTP vulnerable to brute-force leak of internal static ﬁle path components</title>
    <updated>2026-10-04T18:34:57.854620+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: aiohttp</p>
<p>### Summary
Path normalization for static files prevents path traversal, but opens up the ability for an attacker to ascertain the
existence of absolute path components.</p>
<p>### Impact
If an application uses `web.static()` (not recommended for production deployments), it may be possible for an attacker to ascertain the existence of path components.</p>
<p>------</p>
<p>Patch: https://github.com/aio-libs/aiohttp/commit/f2a86fd5ac0383000d1715afddfa704413f0711e</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-54jq-c3m8-4m76"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-1097</id>
    <title>PYSEC-2026-1097 — AIOHTTP vulnerable to brute-force leak of internal static ﬁle path components</title>
    <updated>2026-10-04T18:34:57.854680+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: aiohttp</p>
<p>### Summary
Path normalization for static files prevents path traversal, but opens up the ability for an attacker to ascertain the
existence of absolute path components.</p>
<p>### Impact
If an application uses `web.static()` (not recommended for production deployments), it may be possible for an attacker to ascertain the existence of path components.</p>
<p>------</p>
<p>Patch: https://github.com/aio-libs/aiohttp/commit/f2a86fd5ac0383000d1715afddfa704413f0711e</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-1097"/>
  </entry>
</feed>
