Skip to content

← Actionable
Medium, CVSS 5.3amended

@hono/node-server: Middleware bypass via repeated slashes in serveStatic

CVE-2026-39406GHSA-92pp-h63x-v22m

What to do

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

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-39406: 0.38% estimated exploitation activity in the next 30 days; percentile 31.65 (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 A path handling inconsistency in serveStatic allows protected static files to be accessed by using repeated slashes (//) in the request path. When route-based middleware (e.g., /admin/) is used for authorization, the router may not match paths containing repeated slashes, while serveStatic resolves them as normalized paths. This can lead to a middleware bypass. Details The routing layer and serveStatic handle repeated slashes differently. For example: - /admin/secret.txt = matches /admin/ - //admin/secret.txt = may not match /admin/ This inconsistency allows a request such as: to bypass middleware registered on /admin/ and access protected files. Impact An attacker can access static files that are intended to be protected by route-based middleware by using repeated slashes in the request path. This can lead to unauthorized access to sensitive files under the static root. This issue affects applications that rely on serveStatic together with route-based middleware for access…

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

    Amended from ghsa record GHSA-92pp-h63x-v22m

  2. Revision 1 · created ·

    Published from osv record GHSA-92pp-h63x-v22m

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-39406

Advisory: @hono/node-server: Middleware bypass via repeated slashes in serveStatic
IDs: CVE-2026-39406, GHSA-92pp-h63x-v22m
Record: https://patchnext.com/advisories/cve-2026-39406 (revision 2, source checked 26 Oct 2026, 12:47 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 1.19.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @hono/node-server: affected < 1.19.13; fixed in 1.19.13

## 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-92pp-h63x-v22m (OSV record GHSA-92pp-h63x-v22m lists affected ranges: npm @hono/node-server >=0 <1.19.13 (fixed))
- Verified: https://github.com/advisories/GHSA-92pp-h63x-v22m (GitHub-reviewed advisory GHSA-92pp-h63x-v22m lists affected ranges: npm @hono/node-server >=0 <1.19.13)

Commands are suggestions: review each one before running it.

Loading voting…