<?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-29T22:15:45.999247+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-71554</id>
    <title>CVE-2026-71554 — h2: Duplicate Host header could facilitate request smuggling</title>
    <updated>2026-09-29T22:15:46.197661+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> python-hyper h2</p>
<p>h2 is a pure-Python implementation of a HTTP/2 protocol stack. Versions up to and including 4.4.0 accept request header blocks containing more than one Host header, and forward every Host header to the consuming application. Where the consumer downgrades HTTP/2 to HTTP/1.1, the resulting request carries two Host header lines, providing a request smuggling primitive. This issue is fixed in version 4.4.1.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-71554"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-6hr6-w5qg-qmwg</id>
    <title>GHSA-6hr6-w5qg-qmwg — h2: Duplicate Host header could facilitate request smuggling</title>
    <updated>2026-09-29T22:15:46.197786+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: h2</p>
<p>### Impact
h2 &lt;=4.4.0 accepts request header blocks containing more than one Host header, and forwards every Host header to the consuming application. Where the consumer downgrades HTTP/2 to HTTP/1.1, the resulting request carries two Host header lines, which is a request smuggling primitive (CWE-444).</p>
<p>### Patches
Patched and fixed in v4.4.1</p>
<p>### Workarounds
Users of the h2 library are advised to check and follow HTTP semantics best practices in their application code. h2 provides best effort sanity checks, but ultimately the calling code is responsible to ensure proper and safe usage of HTTP/2 as provided by h2, hyperframe, and hpack.</p>
<p>### References
Similar to the previously disclosed and fixed duplicate content-length issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-6hr6-w5qg-qmwg"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-3628</id>
    <title>PYSEC-2026-3628 — h2: Duplicate Host header could facilitate request smuggling</title>
    <updated>2026-09-29T22:15:46.197851+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: h2</p>
<p>### Impact
h2 &lt;=4.4.0 accepts request header blocks containing more than one Host header, and forwards every Host header to the consuming application. Where the consumer downgrades HTTP/2 to HTTP/1.1, the resulting request carries two Host header lines, which is a request smuggling primitive (CWE-444).</p>
<p>### Patches
Patched and fixed in v4.4.1</p>
<p>### Workarounds
Users of the h2 library are advised to check and follow HTTP semantics best practices in their application code. h2 provides best effort sanity checks, but ultimately the calling code is responsible to ensure proper and safe usage of HTTP/2 as provided by h2, hyperframe, and hpack.</p>
<p>### References
Similar to the previously disclosed and fixed duplicate content-length issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-3628"/>
  </entry>
</feed>
