<?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://vulnerability.circl.lu</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, 02 Oct 2026 17:18:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-29087 — @hono/node-server: Authorization bypass for protected static paths via encoded slashes in Serve Static Middleware</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-29087</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; honojs node-server&lt;/p&gt;
&lt;p&gt;@hono/node-server allows running the Hono application on Node.js. Prior to version 1.19.10, when using @hono/node-server&amp;#39;s static file serving together with route-based middleware protections (e.g. protecting /admin/*), inconsistent URL decoding can allow protected static resources to be accessed without authorization. In particular, paths containing encoded slashes (%2F) may be evaluated differently by routing/middleware matching versus static file path resolution, enabling a bypass where middleware does not run but the static file is still served. This issue has been patched in version 1.19.10.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; honojs node-server&lt;/p&gt;
&lt;p&gt;@hono/node-server allows running the Hono application on Node.js. Prior to version 1.19.10, when using @hono/node-server&amp;#39;s static file serving together with route-based middleware protections (e.g. protecting /admin/*), inconsistent URL decoding can allow protected static resources to be accessed without authorization. In particular, paths containing encoded slashes (%2F) may be evaluated differently by routing/middleware matching versus static file path resolution, enabling a bypass where middleware does not run but the static file is still served. This issue has been patched in version 1.19.10.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-29087</guid>
    </item>
  </channel>
</rss>
