<?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>Sun, 11 Oct 2026 20:20:56 +0000</lastBuildDate>
    <item>
      <title>GHSA-wmmm-f939-6g9c — Hono: Middleware bypass via repeated slashes in serveStatic</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-wmmm-f939-6g9c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: hono&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;A path handling inconsistency in `serveStatic` allows protected static files to be accessed by using repeated slashes (`//`) in the request path.&lt;/p&gt;
&lt;p&gt;When route-based middleware (e.g., `/admin/*`) is used for authorization, the router may not match paths containing repeated slashes, while serveStatic resolves them as normalized paths. This can lead to a middleware bypass.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The routing layer and `serveStatic` handle repeated slashes differently.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;```
/admin/secret.txt =&amp;gt; matches /admin/*
/admin//secret.txt =&amp;gt; may not match /admin/*
```&lt;/p&gt;
&lt;p&gt;However, `serveStatic` may interpret both paths as the same file location (e.g., `admin/secret.txt`) and return the file.&lt;/p&gt;
&lt;p&gt;This inconsistency allows a request such as:&lt;/p&gt;
&lt;p&gt;```
GET //admin/secret.txt
```&lt;/p&gt;
&lt;p&gt;to bypass middleware registered on `/admin/*` and access protected files.&lt;/p&gt;
&lt;p&gt;The issue has been fixed by rejecting paths that contain repeated slashes, ensuring consistent behavior between route matching and static file resolution.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker can access static files that are intended to be protected by route-based middleware by using repeated slashes in the request path.&lt;/p&gt;
&lt;p&gt;This can lead to unauthorized access to sensitive files under the static root.&lt;/p&gt;
&lt;p&gt;This issue affects applications that rely on serveStatic together with route-based middleware for access control.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: hono&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;A path handling inconsistency in `serveStatic` allows protected static files to be accessed by using repeated slashes (`//`) in the request path.&lt;/p&gt;
&lt;p&gt;When route-based middleware (e.g., `/admin/*`) is used for authorization, the router may not match paths containing repeated slashes, while serveStatic resolves them as normalized paths. This can lead to a middleware bypass.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The routing layer and `serveStatic` handle repeated slashes differently.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;```
/admin/secret.txt =&amp;gt; matches /admin/*
/admin//secret.txt =&amp;gt; may not match /admin/*
```&lt;/p&gt;
&lt;p&gt;However, `serveStatic` may interpret both paths as the same file location (e.g., `admin/secret.txt`) and return the file.&lt;/p&gt;
&lt;p&gt;This inconsistency allows a request such as:&lt;/p&gt;
&lt;p&gt;```
GET //admin/secret.txt
```&lt;/p&gt;
&lt;p&gt;to bypass middleware registered on `/admin/*` and access protected files.&lt;/p&gt;
&lt;p&gt;The issue has been fixed by rejecting paths that contain repeated slashes, ensuring consistent behavior between route matching and static file resolution.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker can access static files that are intended to be protected by route-based middleware by using repeated slashes in the request path.&lt;/p&gt;
&lt;p&gt;This can lead to unauthorized access to sensitive files under the static root.&lt;/p&gt;
&lt;p&gt;This issue affects applications that rely on serveStatic together with route-based middleware for access control.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-wmmm-f939-6g9c</guid>
    </item>
  </channel>
</rss>
