<?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>Fri, 13 Nov 2026 05:03:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-126356 — Hono: `validator('form')` skips validation for `multipart/form-data` requests with extra parameters</title>
      <link>https://db.gcve.eu/vuln/cve-2026-126356</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; honojs hono&lt;/p&gt;
&lt;p&gt;Hono is a Web application framework that provides support for any JavaScript runtime. From 4.5.1 until 4.13.16, validator(&amp;#39;form&amp;#39;) uses a strict whole-header pattern that fails to recognize multipart/form-data when its Content-Type includes another legal parameter or extra whitespace after a semicolon. The validation callback receives an empty object even though c.req.parseBody() or c.req.formData() can still parse and expose all submitted fields to the handler. An unauthenticated client can therefore bypass allow-list or required-field checks when the application relies on the form validator and its callback accepts an empty object. application/x-www-form-urlencoded requests are not affected. This issue is fixed in version 4.13.16.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; honojs hono&lt;/p&gt;
&lt;p&gt;Hono is a Web application framework that provides support for any JavaScript runtime. From 4.5.1 until 4.13.16, validator(&amp;#39;form&amp;#39;) uses a strict whole-header pattern that fails to recognize multipart/form-data when its Content-Type includes another legal parameter or extra whitespace after a semicolon. The validation callback receives an empty object even though c.req.parseBody() or c.req.formData() can still parse and expose all submitted fields to the handler. An unauthenticated client can therefore bypass allow-list or required-field checks when the application relies on the form validator and its callback accepts an empty object. application/x-www-form-urlencoded requests are not affected. This issue is fixed in version 4.13.16.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-126356</guid>
    </item>
  </channel>
</rss>
