<?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>Mon, 26 Oct 2026 04:36:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-114629 — Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body par…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-114629</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Web-Simple&lt;/p&gt;
&lt;p&gt;Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parameters.&lt;/p&gt;
&lt;p&gt;Web::Dispatch::ParamParser::get_unpacked_body_from reads an application/x-www-form-urlencoded body using a single read call, with no cap and the return value ignored. Perl&amp;#39;s read grows the buffer to the requested length before reading, so the declared Content-Length determines the allocation.&lt;/p&gt;
&lt;p&gt;An attacker can trigger this through any route whose dispatch specification has a % body-parameter match, such as sub (POST + %name=), sending a Content-Length far larger than the body actually sent. No authentication is involved.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Web-Simple&lt;/p&gt;
&lt;p&gt;Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parameters.&lt;/p&gt;
&lt;p&gt;Web::Dispatch::ParamParser::get_unpacked_body_from reads an application/x-www-form-urlencoded body using a single read call, with no cap and the return value ignored. Perl&amp;#39;s read grows the buffer to the requested length before reading, so the declared Content-Length determines the allocation.&lt;/p&gt;
&lt;p&gt;An attacker can trigger this through any route whose dispatch specification has a % body-parameter match, such as sub (POST + %name=), sending a Content-Length far larger than the body actually sent. No authentication is involved.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-114629</guid>
    </item>
  </channel>
</rss>
