@hono/node-server can't handle "double dots" in URL
@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`.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2024-23340
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 02:24 UTC · Revision 1
Source evidence
@hono/node-server can't handle "double dots" in URL
core-osv · Original sourcePublished 22 Jan 2024, 23:00 UTC
@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`.
osv:CVE-2024-23340
Complete source record
{
"id": "e59f5b72c3b0bd7b44f2a047b0a8673679877fcd27c26357a5f535025e4f5ddf",
"url": "https://osv.dev/vulnerability/CVE-2024-23340",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "@hono/node-server can't handle \"double dots\" in URL",
"summary": "@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`.",
"evidence": "osv:CVE-2024-23340",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2024-23340",
"aliases": [
"CVE-2024-23340",
"GHSA-rjq5-w47x-x359"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/honojs/node-server",
"type": "GIT",
"events": [
{
"introduced": "096e27d07a381eea47bbafc1278950ea0175713a"
},
{
"fixed": "69dd54a0d547c7bccad7d4d365ef033740e3f365"
},
{
"fixed": "dd9b9a9b23e3896403c90a740e7f1f0892feb402"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:hono:node-server:*:*:*:*:*:node.js:*:*",
"range": [
{
"introduced": "1.3.0"
},
{
"fixed": "1.4.1"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "dd9b9a9b23e3896403c90a740e7f1f0892feb402"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v1.4.0",
"v1.3.5",
"v1.3.4",
"v1.3.3",
"v1.3.2",
"v1.3.1",
"v1.3.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-23340.json"
}
}
],
"modified": "2026-10-28T02:30:25.142087947Z",
"provider": "osv",
"references": [
"https://github.com/honojs/node-server/blob/8cea466fd05e6d2e99c28011fc0e2c2d3f3397c9/src/request.ts#L43-L45",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/23xxx/CVE-2024-23340.json",
"https://github.com/honojs/node-server/security/advisories/GHSA-rjq5-w47x-x359",
"https://nvd.nist.gov/vuln/detail/CVE-2024-23340",
"https://github.com/honojs/node-server/commit/dd9b9a9b23e3896403c90a740e7f1f0892feb402"
],
"provider_metadata": {
"cwe_ids": [
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/23xxx/CVE-2024-23340.json"
}
},
"related_cves": [
{
"value": "CVE-2024-23340",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 491868,
"published_at": "2024-01-22T23:00:34.51+00:00"
}