<?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-29T06:35:38.006909+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-2026-34520</id>
    <title>CVE-2026-34520 — AIOHTTP: C parser (llhttp) accepts null bytes and control characters in response header values - header injection / sec…</title>
    <updated>2026-09-29T06:35:38.011568+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. Prior to version 3.13.4, the C parser (the default for most installs) accepted null bytes and control characters in response headers. This issue has been patched in version 3.13.4.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-34520"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-63hf-3vf5-4wqf</id>
    <title>GHSA-63hf-3vf5-4wqf — AIOHTTP's C parser (llhttp) accepts null bytes and control characters in response header values - header injection/secu…</title>
    <updated>2026-09-29T06:35:38.011781+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 C parser (the default for most installs) accepted null bytes and control characters in request headers.</p>
<p>### Impact</p>
<p>An attacker could send header values that are interpreted differently than expected due to the presence of control characters. For example, `request.url.origin()` may return a different value than the raw Host header, or what a reverse proxy interpreted it as., potentially resulting in some kind of security bypass.</p>
<p>-----</p>
<p>Patch: https://github.com/aio-libs/aiohttp/commit/9370b9714a7a56003cacd31a9b4ae16eab109ba4</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-63hf-3vf5-4wqf"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-2102</id>
    <title>PYSEC-2026-2102</title>
    <updated>2026-09-29T06:35:38.011907+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: aiohttp</p>
<p>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, the C parser (the default for most installs) accepted null bytes and control characters in response headers. This issue has been patched in version 3.13.4.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-2102"/>
  </entry>
</feed>
