fix(deps): update dependency @hono/node-server to v2 [security] by renovate[bot] · Pull Request #2727 · heygen-com/hyperframes

renovate · 2026-07-22T00:03:24Z

This PR contains the following updates:

Package	Change	Age	Confidence
@hono/node-server	`^1.13.0` → `^2.0.5`
@hono/node-server	`^1.8.0` → `^2.0.5`

Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)

GHSA-frvp-7c67-39w9

More information

Details

The same as the hono core Path traversal in serve-static on Windows via encoded backslash (%5C).

Summary

On Windows hosts, an encoded backslash (%5C) in the request path decodes to \, which the Windows path resolver treats as a separator. serve-static then resolves a single URL segment such as admin\secret.txt into a nested file under the root and serves it, letting an attacker read static files meant to be protected behind prefix-mounted middleware. Directory escape (..) remains blocked.

Details

The router splits paths only on /, so /admin%5Csecret.txt is one segment and middleware on /admin/* does not run. The serve-static guard rejects ./.. and consecutive separators but lets a lone \ through; on Windows the file resolver re-splits it into the protected subtree.

This affects Windows hosts serving static files via the Node, Bun, or Deno adapters that guard a static subtree with prefix-mounted middleware.

Impact

An unauthenticated attacker can read static files under a middleware-guarded prefix on Windows hosts. The read stays within the configured root; escape outside the root is not possible.

Severity

CVSS Score: 5.9 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Release Notes

honojs/node-server (@hono/node-server)

`v2.0.5`

Compare Source

Security Fix

Fixed a security issue in Serve Static Middleware where prefix-mounted middleware could be bypassed on Windows. This only affects applications running on Windows that use Serve Static Middleware. Affected users are encouraged to upgrade to this version.

See GHSA-frvp-7c67-39w9 for details.

`v2.0.4`

Compare Source

What's Changed

fix: stub ws types to prevent them leaking in public types by @BlankParticle in #359

Full Changelog: honojs/node-server@v2.0.3...v2.0.4

`v2.0.3`

Compare Source

What's Changed

chore(ci): update GitHub Actions versions by @BlankParticle in #352
docs: Align the ServeStaticOptions comment with the current spec by @kakkokari-gtyih in #356
fix: preserve headers mutated after raw Response construction by @abdulmunimjemal in #357

New Contributors

@kakkokari-gtyih made their first contribution in #356
@abdulmunimjemal made their first contribution in #357

Full Changelog: honojs/node-server@v2.0.2...v2.0.3

`v2.0.2`

Compare Source

What's Changed

fix(serve-static): stop using file birthtime for Date header by @usualoma in #350
fix: handle serveStatic stream fallback backpressure by @usualoma in #351

Full Changelog: honojs/node-server@v2.0.1...v2.0.2

`v2.0.1`

Compare Source

What's Changed

fix: forward Hono response headers during WebSocket upgrade by @gentamura in #346

New Contributors

@gentamura made their first contribution in #346

Full Changelog: honojs/node-server@v2.0.0...v2.0.1

`v2.0.0`

Compare Source

Now, we release the second major version of the Hono Node.js adapter 🎉 🎉 🎉

The Hono Node.js adapter is now up to 2.3x faster

v2 of the Hono Node.js adapter reaches up to 2.3x the throughput of v1 — that's the peak number, measured on the body-parsing scenario of bun-http-framework-benchmark. The other scenarios (Ping, Query) get a smaller but real boost too.

Install or upgrade with:

npm i @&#8203;hono/node-server@latest

v2

The Node.js adapter is going through a major version bump to v2. That said, the public API stays the same — the headline of this release is the large performance improvement described above.

What does the Node.js adapter do?

A quick refresher on what the Node.js adapter actually does — it exists so that Hono applications can run on Node.js. Hono is built on the Web Standards APIs, but you cannot serve those directly from Node.js. The adapter bridges the Web Standards APIs and the Node.js APIs, which is what lets a Hono app — and more generally a Web-Standards-style app — run on top of Node.js.

If you write the following code and run node ./index.js, a server starts up on localhost:3000. And it really is plain Node.js underneath.

import { Hono } from 'hono'
import { serve } from '@&#8203;hono/node-server'

const app = new Hono()
app.get('/', (c) => c.text('Hello World!'))

serve(app)

The early performance story

The very first implementation of the Node.js adapter looked roughly like this in pseudocode:

export const getRequestListener = (fetchCallback: FetchCallback) => {
  return async (incoming: IncomingMessage, outgoing: ServerResponse) => {
    const method = incoming.method || 'GET'
    const url = `http://${incoming.headers.host}${incoming.url}`

    // ...

    const init = {
      method: method,
      headers: headerRecord,
    }

    // app is a Hono application
    const res = await app.fetch(new Request(url, init))
    const buffer = await res.arrayBuffer()
    outgoing.writeHead(res.status, resHeaderRecord)
    outgoing.end(new Uint8Array(buffer))
  }
}

So the flow was:

a request comes in as an IncomingMessage
it gets converted into a Request object and handed to the app
the Response returned by the app is written back to the outgoing ServerResponse

In diagram form:

IncomingMessage => Request => app => Response => ServerResponse

This is, frankly, inefficient. So whenever Hono went head-to-head with other Node.js frameworks we kept losing — all we could do was shrug and say "well, it's slow on Node.js."

Introducing LightweightRequest / LightweightResponse

The huge step forward that fixed this was a legendary PR from @usualoma:

#95

It made things up to 2.7x faster.

I previously wrote about this in detail in this post:

https://zenn.dev/yusukebe/articles/7ac501716ae1f7?locale=en

In short, the trick is wonderfully simple. It just follows the golden rule of performance tuning: don't do work you don't have to do. Lightweight versions of Request and Response are constructed and used first — and that path is fast. Only when something actually needs the contents of the Request, e.g. when you call req.json(), does a real new Request() get instantiated under the hood and used from then on. The result is fast, and behavior stays correct.

…but body parsing was still slow

"Fast" here was for a very simple "Hello World" benchmark — a GET that just returns text.

There are many ways to benchmark, but the one we tend to reach for is this:

https://github.com/SaltyAom/bun-http-framework-benchmark

It tests three scenarios: Ping, Query, and Body. Let's pit Hono against the major Node.js frameworks:

As you can see, the Body case is very slow. The handler being measured is essentially this:

import { Hono } from 'hono'
import { serve } from '@&#8203;hono/node-server'

const app = new Hono()

app.post('/json', async (c) => {
  const data = await c.req.json()
  return c.json(data)
})

serve(app)

c.req.json() is the slow part. The reason is well understood: inside the Node.js adapter, when json() is called the LightweightRequest path can't be used, so a real new Request() ends up being constructed.

perf: optimize request body reading

The 2.3x figure above comes from one PR specifically — PR #301 by @mgcrea:

The PR bundles a few changes, but the key one is "optimize request body reading". Quoting from the PR description:

The fix overrides text(), json(), arrayBuffer(), and blob() on the request prototype to read directly from the Node.js IncomingMessage using event-based I/O.

In other words, in the json() case above, we no longer convert into a Request at all — we read the body straight off the Node.js APIs. A classic fast path. That alone gives a large jump in body-parsing throughput.

The same PR also includes two other tuning improvements:

URL construction fast-path — skip building a URL object except in edge cases
buildOutgoingHttpHeaders optimization — skip the set-cookie header comparison when there are no cookies

v2 ships several other performance PRs as well — newHeadersFromIncoming and signal fast-paths, Response fast-paths and responseViaCache improvements, method-key caching, a regex-based buildUrl rewrite, and more (see the full list below). They all add up, but #301 is by far the largest single contributor, which is why it gets the spotlight here.

v2 performance

Now let's measure the final v2 build.

First, comparing against the v1 Node.js adapter. dev here is v2. Body improves by 2.3x, and the other scenarios get faster too:

Next, the same comparison against other frameworks. With the Body score jumping, Hono passes Koa and Fastify and takes first place:

[!CAUTION]
Updated: The h3 entry in the earlier framework comparison was an older snapshot. Its successor srvx now ships a FastResponse mode, and in srvx's own benchmark (h3js/srvx/test/bench-node) srvx-fast (≈68,560 req/sec) beats hono-fast (≈59,477 req/sec). The methodology is different from the benchmarks above, but worth being upfront: with FastResponse enabled, srvx is faster than Hono v2 in that setup.

Breaking changes

There are two breaking changes in v2.

Dropped support for Node.js v18

Node.js v18 reached end-of-life, so v2 requires Node.js v20 or later.

Removed the Vercel adapter

The Vercel adapter (@hono/node-server/vercel) has been removed. It is no longer needed for Vercel's modern runtimes, so the recommendation is to deploy without it.

If you still need the previous behavior, the old adapter was a one-liner on top of getRequestListener and you can write the same thing in your own project:

import type { Hono } from 'hono'
import { getRequestListener } from '@&#8203;hono/node-server'

export const handle = (app: Hono) => {
  return getRequestListener(app.fetch)
}

Then use it the same way you used handle from @hono/node-server/vercel before.

All changes

A full list of what landed in PR #316.

Performance

perf: optimize request body reading and URL construction (#301) by @mgcrea
perf: optimize buildOutgoingHttpHeaders for the common case (#301) by @mgcrea
perf(request): cache method key (#319) by @yusukebe
perf(url): mark host with port : as safe host (#320) by @yusukebe
perf(request): optimize newHeadersFromIncoming and signal fast-path (#332) by @GavinMeierSonos
perf(response, listener): Response fast-paths and responseViaCache improvements (#333) by @GavinMeierSonos
perf: replace Uint8Array lookup tables with regex in buildUrl (#345) by @usualoma

Features

feat: first-class support for WebSockets (#328) by @BlankParticle

Breaking changes

feat: end support for Node.js v18 (#317) by @yusukebe
feat!: obsolete the Vercel adapter (#335) by @yusukebe

Fixes & refactors

fix: more strictly determine when new URL() should be used (#310) by @usualoma
refactor: improved compatibility with the Web Standard Request object (#311) by @usualoma
fix(request): return an error object instead of throwing (#318) by @usualoma
refactor: improve handling of null body in response (#341) by @usualoma
fix: ensure close handler is attached for Blob/ReadableStream cacheable responses (#342) by @usualoma
fix: improve Response.json() and Response.redirect() spec compliance and efficiency (#343) by @usualoma

Build & tooling

build: migrate from tsup to tsdown (#302) by @tommy-ish
feat(test): migrate Jest to Vitest (#303) by @koralle
fix: only build exported entrypoints (#323) by @BlankParticle
chore: add type: module to package.json (#336) by @yusukebe

Wrap-up

So that's v2 of the Node.js adapter — significantly faster, with the same API. Just upgrading should give you a real performance boost. No more "Hono is slow on Node.js" excuses. Please use Hono — fast not only on Cloudflare, Bun, and Deno, but now also on Node.js.

`v1.19.15`

Compare Source

`v1.19.14`

Compare Source

What's Changed

fix: add custom inspect to lightweight Request/Response to prevent TypeError on console.log by @usualoma in #340

Full Changelog: honojs/node-server@v1.19.13...v1.19.14

`v1.19.13`

Compare Source

Security Fix

Fixed an issue in Serve Static Middleware where inconsistent handling of repeated slashes (//) between the router and static file resolution could allow middleware to be bypassed. Users of Serve Static Middleware are encouraged to upgrade to this version.

See GHSA-92pp-h63x-v22m for details.

`v1.19.12`

Compare Source

What's Changed

chore: ignore claude setting by @yusukebe in #314
fix: request draining for early 413 responses by @usualoma in #329

Full Changelog: honojs/node-server@v1.19.11...v1.19.12

`v1.19.11`

Compare Source

What's Changed

fix: do not overwrite Content-Length in the fast path pattern if Content-Length already exists. by @usualoma in #309

Full Changelog: honojs/node-server@v1.19.10...v1.19.11

`v1.19.10`

Compare Source

Security Fix

Fixed an authorization bypass in Serve Static Middleware caused by inconsistent URL decoding (%2F handling) between the router and static file resolution. Users of Serve Static Middleware are encouraged to upgrade to this version.

See GHSA-wc8c-qw6v-h7f6 for details.

`v1.19.9`

Compare Source

What's Changed

fix(globals): Stop overwriting global.fetch by @usualoma in #295

Full Changelog: honojs/node-server@v1.19.8...v1.19.9

`v1.19.8`

Compare Source

What's Changed

docs: add guide for listening to UNIX domain socket by @TransparentLC in #292
fix(serve-static): Use Readable.toWeb in serveStatic by @otya128 in #293

New Contributors

@TransparentLC made their first contribution in #292
@otya128 made their first contribution in #293

Full Changelog: honojs/node-server@v1.19.7...v1.19.8

`v1.19.7`

Compare Source

What's Changed

fix: Fix for hono issue 4563 - incorrect content-length after following symlink by @tshmieldev in #290
chore: add configVersion to bun.lock by @yusukebe in #291

New Contributors

@tshmieldev made their first contribution in #290

Full Changelog: honojs/node-server@v1.19.6...v1.19.7

`v1.19.6`

Compare Source

What's Changed

fix(serve-static): fix onFound timing by @usualoma in #286

Full Changelog: honojs/node-server@v1.19.5...v1.19.6

`v1.19.5`

Compare Source

What's Changed

fix: cancel a readable stream if a writable stream is closed before a readable stream is closed. by @usualoma in #280

Full Changelog: honojs/node-server@v1.19.4...v1.19.5

`v1.19.4`

Compare Source

What's Changed

fix(serve-static): Add error handling in createStreamBody by @thongdoan in #278

New Contributors

@thongdoan made their first contribution in #278

Full Changelog: honojs/node-server@v1.19.3...v1.19.4

`v1.19.3`

Compare Source

What's Changed

fix: Refactor promise check for response handling by @kay-is in #277

New Contributors

@kay-is made their first contribution in #277

Full Changelog: honojs/node-server@v1.19.2...v1.19.3

`v1.19.2`

Compare Source

What's Changed

fix: better handle range parse to avoid NaN error by @zwpaper in #276

New Contributors

@zwpaper made their first contribution in #276

Full Changelog: honojs/node-server@v1.19.1...v1.19.2

`v1.19.1`

Compare Source

What's Changed

fix: Keep lightweight request even if accessing method, url or headers by @usualoma in #274
chore: add packageManager field in package.json by @yusukebe in #275

Full Changelog: honojs/node-server@v1.19.0...v1.19.1

`v1.19.0`

Compare Source

What's Changed

feat: add log when directory does not exists by @Its-Just-Nans in #273

New Contributors

@Its-Just-Nans made their first contribution in #273

Full Changelog: honojs/node-server@v1.18.2...v1.19.0

`v1.18.2`

Compare Source

What's Changed

fix: Skip content-length assignment when transfer-encoding is chunked. by @usualoma in #271

Full Changelog: honojs/node-server@v1.18.1...v1.18.2

`v1.18.1`

Compare Source

What's Changed

fix(listener): Limit retries to a maximum of three. by @usualoma in #267

Full Changelog: honojs/node-server@v1.18.0...v1.18.1

`v1.18.0`

Compare Source

What's Changed

feat: always respond res.body by @usualoma in #262
ci: add Node.js v24 for CI by @yusukebe in #263
fix(listener): In Node.js v24, some response bodies are not read to the end until the next task queue. by @usualoma in #265

Full Changelog: honojs/node-server@v1.17.1...v1.18.0

`v1.17.1`

Compare Source

What's Changed

fix: handle client disconnection without canceling stream by @yusukebe in #258
fix: improve serve-static function by @usualoma in #261

Full Changelog: honojs/node-server@v1.17.0...v1.17.1

`v1.17.0`

Compare Source

What's Changed

docs: separate description of autoCleanupIncoming by @usualoma in #255
chore: rename server_socket.test.ts to server-socket.test.ts by @yusukebe in #256
feat(serve-static): support absolute path by @yusukebe in #257

Full Changelog: honojs/node-server@v1.16.0...v1.17.0

`v1.16.0`

Compare Source

What's Changed

feat: Clean up the incoming object if the request is not completely finished. by @usualoma in #252

Full Changelog: honojs/node-server@v1.15.0...v1.16.0

`v1.15.0`

Compare Source

What's Changed

feat(serve-static): pass context to rewriteRequestPath by @yusukebe in #247

Full Changelog: honojs/node-server@v1.14.4...v1.15.0

`v1.14.4`

Compare Source

What's Changed

fix: flush headers before sending data via readable stream by @usualoma in #245

Full Changelog: honojs/node-server@v1.14.3...v1.14.4

`v1.14.3`

Compare Source

What's Changed

fix: set RequestError name properly by @yusukebe in #243

Full Changelog: honojs/node-server@v1.14.2...v1.14.3

`v1.14.2`

Compare Source

What's Changed

perf: keep using the lightweight Response object when retrieving headers, status, and ok, and then drop the getInternalBody function. by @usualoma in #242

Full Changelog: honojs/node-server@v1.14.1...v1.14.2

`v1.14.1`

Compare Source

What's Changed

fix: Handle Response Errors Correctly by @jpulec in #236

New Contributors

@jpulec made their first contribution in #236

Full Changelog: honojs/node-server@v1.14.0...v1.14.1

`v1.14.0`

Compare Source

What's Changed

chore: use Bun as a package manager by @yusukebe in #224
fix: #230 use node:fs specifier prefix vs. fs import by @firxworx in #231
feat: accept absolute-form URI for request-target by @usualoma in #232
fix: fix the return type of responseViaCache by @yusukebe in #234

New Contributors

@firxworx made their first contribution in #231

Full Changelog: honojs/node-server@v1.13.8...v1.14.0

`v1.13.8`

Compare Source

What's Changed

fix: export ServerOptions type by @aryasaatvik in #222
fix: re-read request body from incoming.rawBody if available by @usualoma in #223
fix: Avoid error if connection is aborted before internal request object is created by @usualoma in #221

New Contributors

@aryasaatvik made their first contribution in #222

Full Changelog: honojs/node-server@v1.13.7...v1.13.8

`v1.13.7`

Compare Source

What's Changed

fix: detection of client premature close by @Tomas2D in #218

New Contributors

@Tomas2D made their first contribution in #218

Full Changelog: honojs/node-server@v1.13.6...v1.13.7

`v1.13.6`

Compare Source

What's Changed

fix: conninfo returns server IP by @nakasyou in #216

Full Changelog: honojs/node-server@v1.13.5...v1.13.6

`v1.13.5`

Compare Source

What's Changed

fix(utils): accept HeadersInit, null, undefined in buildOutgoingHttpHeaders by @usualoma in #212

Full Changelog: honojs/node-server@v1.13.4...v1.13.5

`v1.13.4`

Compare Source

What's Changed

fix: TypeError: headers is not iterable by @mjad218 in #210

New Contributors

@mjad218 made their first contribution in #210

Full Changelog: honojs/node-server@v1.13.3...v1.13.4

`v1.13.3`

Compare Source

What's Changed

fix(serve-static): add error handler for decoding uri components by @alumowa in #208

New Contributors

@alumowa made their first contribution in #208

Full Changelog: honojs/node-server@v1.13.2...v1.13.3

`v1.13.2`

Compare Source

What's Changed

fix(serve): support ipv6 by default by @sinasab in #206

New Contributors

@sinasab made their first contribution in #206

Full Changelog: honojs/node-server@v1.13.1...v1.13.2

`v1.13.1`

Compare Source

What's Changed

fix(serve-static): use application/octet-stream if the mime type is not detected by @usualoma in #201

Full Changelog: honojs/node-server@v1.13.0...v1.13.1

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate Bot added the security label Jul 22, 2026

renovate Bot force-pushed the renovate/npm-hono-node-server-vulnerability branch from 477bdeb to fae94b8 Compare July 22, 2026 00:08

renovate Bot changed the title ~~fix(deps): update dependency @hono/node-server to ^1.19.14 [security]~~ fix(deps): update dependency @hono/node-server to v2 [security] Jul 22, 2026

renovate Bot force-pushed the renovate/npm-hono-node-server-vulnerability branch from fae94b8 to 9158487 Compare July 22, 2026 00:38

renovate Bot changed the title ~~fix(deps): update dependency @hono/node-server to v2 [security]~~ fix(deps): update dependency @hono/node-server to ^1.19.14 [security] Jul 22, 2026

renovate Bot force-pushed the renovate/npm-hono-node-server-vulnerability branch from 9158487 to fda3d1c Compare July 22, 2026 21:47

renovate Bot changed the title ~~fix(deps): update dependency @hono/node-server to ^1.19.14 [security]~~ fix(deps): update dependency @hono/node-server to v2 [security] Jul 22, 2026

renovate Bot force-pushed the renovate/npm-hono-node-server-vulnerability branch from fda3d1c to 7b652e2 Compare July 22, 2026 22:46

renovate Bot changed the title ~~fix(deps): update dependency @hono/node-server to v2 [security]~~ fix(deps): update dependency @hono/node-server to ^1.19.14 [security] Jul 22, 2026

renovate Bot force-pushed the renovate/npm-hono-node-server-vulnerability branch from 7b652e2 to 19a0264 Compare July 23, 2026 00:50