<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T03:16:23.555823+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/ghsa-35p6-xmwp-9g52</id>
    <title>GHSA-35p6-xmwp-9g52 — undici vulnerable to HTTP response queue poisoning via keep-alive socket reuse</title>
    <updated>2026-09-30T03:16:23.557228+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: undici</p>
<p>## Impact</p>
<p>Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests.</p>
<p>This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse.</p>
<p>## Patches</p>
<p>Upgrade to undici v6.27.0, v7.28.0 or v8.5.0.</p>
<p>## Workarounds</p>
<p>Disable keep-alive connection reuse by setting `keepAliveTimeout: 0` on the Client or Pool.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-35p6-xmwp-9g52"/>
  </entry>
</feed>
