Node.js Adapter for Hono: Path traversal in serve-static on Windows via encoded backslash (%5C)
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@hono/node-server 2.0.5, 1.19.15), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- >= 2.0.0, < 2.0.5< 1.19.15
- Fixed in
- 1.19.15, 2.0.5
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-frvp-7c67-39w9 lists affected ranges: npm @hono/node-server >=2.0.0 =0 <1.19.15 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-frvp-7c67-39w9 lists affected ranges: npm @hono/node-server >=2.0.0 =0 <1.19.15
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-frvp-7c67-39w9
- Revision 1 · created ·
Published from osv record GHSA-frvp-7c67-39w9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-frvp-7c67-39w9 Advisory: Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`) IDs: GHSA-frvp-7c67-39w9 Record: https://patchnext.com/advisories/ghsa-frvp-7c67-39w9 (revision 2, source checked 26 Oct 2026, 13:01 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @hono/node-server 2.0.5, 1.19.15. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @hono/node-server: affected >= 2.0.0, < 2.0.5; < 1.19.15; fixed in 1.19.15, 2.0.5 ## Suggested inspection (read-only) - `npm ls @hono/node-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @hono/node-server. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-frvp-7c67-39w9 (OSV record GHSA-frvp-7c67-39w9 lists affected ranges: npm @hono/node-server >=2.0.0 =0 <1.19.15 (fixed)) - Verified: https://github.com/advisories/GHSA-frvp-7c67-39w9 (GitHub-reviewed advisory GHSA-frvp-7c67-39w9 lists affected ranges: npm @hono/node-server >=2.0.0 =0 <1.19.15) Commands are suggestions: review each one before running it.
Loading voting…