<?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://db.gcve.eu</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>Tue, 27 Oct 2026 19:10:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-115823 — Starman versions before 0.4019 for Perl send response bodies for HEAD requests, desynchronizing responses on keep-alive…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-115823</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Starman&lt;/p&gt;
&lt;p&gt;Starman versions before 0.4019 for Perl send response bodies for HEAD requests, desynchronizing responses on keep-alive connections.&lt;/p&gt;
&lt;p&gt;For a HEAD request Starman omits chunked framing but still writes the body returned by the application, on both the array and streaming response paths. Responses with a 1xx, 204 or 304 status also carry the body.&lt;/p&gt;
&lt;p&gt;On a keep-alive or pipelined connection the client reads those bytes as the start of the next response. A front-end proxy that reuses upstream connections may then pair responses with the wrong requests.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Starman&lt;/p&gt;
&lt;p&gt;Starman versions before 0.4019 for Perl send response bodies for HEAD requests, desynchronizing responses on keep-alive connections.&lt;/p&gt;
&lt;p&gt;For a HEAD request Starman omits chunked framing but still writes the body returned by the application, on both the array and streaming response paths. Responses with a 1xx, 204 or 304 status also carry the body.&lt;/p&gt;
&lt;p&gt;On a keep-alive or pipelined connection the client reads those bytes as the start of the next response. A front-end proxy that reuses upstream connections may then pair responses with the wrong requests.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-115823</guid>
    </item>
  </channel>
</rss>
