https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 09:28:46 +0000 https://vulnerability.circl.lu/vuln/ghsa-q5qw-h33p-qvwr <p><strong>Affected:</strong> npm: hono</p> <p>## Summary</p> <p>When using `serveStatic` together with route-based middleware protections (e.g. `app.use(&#39;/admin/*&#39;, ...)`), inconsistent URL decoding allowed protected static resources to be accessed without authorization.</p> <p>The router used `decodeURI`, while `serveStatic` used `decodeURIComponent`. This mismatch allowed paths containing encoded slashes (`%2F`) to bypass middleware protections while still resolving to the intended filesystem path.</p> <p>## Details</p> <p>The routing layer preserved `%2F` as a literal string, while `serveStatic` decoded it into `/` before resolving the file path.</p> <p>Example:</p> <p>Request: `/admin%2Fsecret.html`</p> <p>- Router sees: `/admin%2Fsecret.html` → does not match `/admin/*` - Static handler resolves: `/admin/secret.html`</p> <p>As a result, static files under the configured static root could be served without triggering route-based protections.</p> <p>This only affects applications that both:</p> <p>- Protect subpaths using route-based middleware, and - Serve files from the same static root using `serveStatic`.</p> <p>This does **not** allow access outside the static root and is **not** a path traversal vulnerability.</p> <p>## Impact</p> <p>An unauthenticated attacker could bypass route-based authorization for protected static resources by supplying paths containing encoded slashes.</p> <p>Applications relying solely on route-based middleware to protect static subpaths may have exposed those resources.</p> <p><strong>Affected:</strong> npm: hono</p> <p>## Summary</p> <p>When using `serveStatic` together with route-based middleware protections (e.g. `app.use(&#39;/admin/*&#39;, ...)`), inconsistent URL decoding allowed protected static resources to be accessed without authorization.</p> <p>The router used `decodeURI`, while `serveStatic` used `decodeURIComponent`. This mismatch allowed paths containing encoded slashes (`%2F`) to bypass middleware protections while still resolving to the intended filesystem path.</p> <p>## Details</p> <p>The routing layer preserved `%2F` as a literal string, while `serveStatic` decoded it into `/` before resolving the file path.</p> <p>Example:</p> <p>Request: `/admin%2Fsecret.html`</p> <p>- Router sees: `/admin%2Fsecret.html` → does not match `/admin/*` - Static handler resolves: `/admin/secret.html`</p> <p>As a result, static files under the configured static root could be served without triggering route-based protections.</p> <p>This only affects applications that both:</p> <p>- Protect subpaths using route-based middleware, and - Serve files from the same static root using `serveStatic`.</p> <p>This does **not** allow access outside the static root and is **not** a path traversal vulnerability.</p> <p>## Impact</p> <p>An unauthenticated attacker could bypass route-based authorization for protected static resources by supplying paths containing encoded slashes.</p> <p>Applications relying solely on route-based middleware to protect static subpaths may have exposed those resources.</p> https://vulnerability.circl.lu/vuln/ghsa-q5qw-h33p-qvwr