@hono/node-server is an adapter that allows users to run Hono applications on Node.js. Since v1.3.0, @hono/node-server has used its own Request object with `url` behavior that is unexpected. In the standard API, if the URL contains `..`, here called "double dots", the URL string returned by Request will be in the resolved path. However, the `url` in @hono/node-server's Request as does not resolve double dots, so `http://localhost/static/.. /foo.txt` is returned. This causes vulnerabilities when using `serveStatic`. Modern web browsers and a latest `curl` command resolve double dots on the client side, so this issue doesn't affect those using either of those tools. However, problems may occur if accessed by a client that does not resolve them. Version 1.4.1 includes the change to fix this issue. As a workaround, don't use `serveStatic`.

Affected: npm: @hono/node-server

### Impact

Since v1.3.0, we use our own Request object. This is great, but the `url` behavior is unexpected.

In the standard API, if the URL contains `..`, here called "double dots", the URL string returned by Request will be in the resolved path.

```ts const req = new Request('http://localhost/static/../foo.txt') // Web-standards console.log(req.url) // http://localhost/foo.txt ```

However, the `url` in our Request does not resolve double dots, so `http://localhost/static/.. /foo.txt` is returned.

```ts const req = new Request('http://localhost/static/../foo.txt') console.log(req.url) // http://localhost/static/../foo.txt ```

It will pass unresolved paths to the web application. This causes vulnerabilities like #123 when using `serveStatic`.

Note: Modern web browsers and a latest `curl` command resolve double dots on the client side, so it does not affect you if the user uses them. However, problems may occur if accessed by a client that does not resolve them.

### Patches

"v1.4.1" includes the change to fix this issue.

### Workarounds

Don't use `serveStatic`.