Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

@hono/node-server: serveStatic decodes the request path a second time, leading to bypass of middleware on static paths

CVE-2026-118663GHSA-rmxm-3fg6-px4f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@hono/node-server 2.1.3), 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.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-118663: 0.35% estimated exploitation activity in the next 30 days; percentile 29.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary `serveStatic` decodes the request path a second time after Hono has already decoded it for routing. A crafted request can be routed as one path and served as another, so middleware mounted on a static prefix does not run for a file under that prefix.

Details Hono decodes the request path once before routing. `serveStatic` decoded it again before resolving the file. With a malformed percent-encoded sequence, the first decode leaves part of the path encoded, the router matches the encoded form, and the second decode resolves the real directory. The file is still resolved inside the configured root; this is not a traversal outside it.

Impact An unauthenticated attacker may reach static files without the middleware on their prefix running, for example an authentication check. This affects applications that mount middleware on part of the directory served by `serveStatic`. Applications that serve only public files are not affected.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-rmxm-3fg6-px4f

  2. Revision 1 · created ·

    Published from ghsa record GHSA-rmxm-3fg6-px4f

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-118663

Advisory: @hono/node-server: `serveStatic` decodes the request path a second time, leading to bypass of middleware on static paths
IDs: CVE-2026-118663, GHSA-rmxm-3fg6-px4f
Record: https://patchnext.com/advisories/cve-2026-118663 (revision 2, source checked 29 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
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.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @hono/node-server: affected >= 1.19.10, < 2.1.3; fixed in 2.1.3

## 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://github.com/advisories/GHSA-rmxm-3fg6-px4f (GitHub-reviewed advisory GHSA-rmxm-3fg6-px4f lists affected ranges: npm @hono/node-server >=1.19.10 <2.1.3)
- Verified: https://osv.dev/vulnerability/GHSA-rmxm-3fg6-px4f (OSV record GHSA-rmxm-3fg6-px4f lists affected ranges: npm @hono/node-server >=1.19.10 <2.1.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…