Public vulnerability disclosure

CVE-2026-126210

@hono/node-server: Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy

publishedCWE-436

@hono/node-server allows running the Hono application on Node.js. Prior to 1.19.18 and from 2.0.0 until 2.1.6, the server passes a raw request-target containing a backslash in its path to the WHATWG URL parser, which treats the backslash as a path separator and resolves dot segments. A reverse proxy, load balancer, or web application firewall that preserves the backslash and applies path-based rules to the original request can therefore permit a request that the application normalizes to a blocked route. This lets an unauthenticated client reach route content that the upstream component was intended to deny, while Hono application access controls are unaffected because they operate on the normalized path. This issue is fixed in versions 1.19.18 and 2.1.6.

Technical severity5.3 mediumCVSS 3.1 · CNA: GitHub_M
Published2026-11-12Source updated 2026-11-13
Collected2026-11-144 attributed sources

Fixes and workarounds

Fix

@hono/node-server (npm): OSV reports a fixed version 2.1.6. Check the advisory for supported release branches.

Source: OSV GHSA-jpvv-r467-5p4w

Fix

@hono/node-server (npm): OSV reports a fixed version 1.19.18. Check the advisory for supported release branches.

Source: OSV GHSA-jpvv-r467-5p4w

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
node-server
honojs
>= 2.0.0, < 2.1.6 (affected)
< 1.19.18 (affected)
CNA: GitHub_M
@hono/node-server

@hono/node-server
npm
≥ 2.0.0; < 2.1.6 (affected, semver); OSV events: introduced 2.0.0; fixed 2.1.6
Source events (semver)
[
  {
    "introduced": "2.0.0"
  },
  {
    "fixed": "2.1.6"
  }
]

Other versions: unaffected
OSV GHSA-jpvv-r467-5p4w
@hono/node-server

@hono/node-server
npm
≥ 0; < 1.19.18 (affected, semver); OSV events: introduced 0; fixed 1.19.18
Source events (semver)
[
  {
    "introduced": "0"
  },
  {
    "fixed": "1.19.18"
  }
]

Other versions: unaffected
OSV GHSA-jpvv-r467-5p4w

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 5.3
medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCNA: GitHub_M
3.1 / 5.3
medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NNVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide