Named path parameters can be overridden in TrieRouter

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.2 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L

EPSS

• CVE-2023-50710: 0.64% estimated exploitation activity in the next 30 days; percentile 50.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The clients may override named path parameter values from previous requests if the application is using TrieRouter. So, there is a risk that a privileged user may use unintended parameters when deleting REST API resources. TrieRouter is used either explicitly or when the application matches a pattern that is not supported by the default RegExpRouter. The code to reproduce it. The server side application: The client code which makes requests to the server application: The results: Patches "v3.11.7" includes the change to fix this issue. Workarounds Don't use TrieRouter directly. References Router options on the Hono website: https://hono.dev/api/hono#router-option

Published by the source

15 Dec 2023, 02:45 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:30 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-f6gv-hh8j-q8vq

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f6gv-hh8j-q8vq

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

# Patch Next advisory brief: CVE-2023-50710

Advisory: Named path parameters can be overridden in TrieRouter
IDs: CVE-2023-50710, GHSA-f6gv-hh8j-q8vq
Record: https://patchnext.com/advisories/cve-2023-50710 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hono 3.11.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm hono: affected < 3.11.7; fixed in 3.11.7

## Suggested inspection (read-only)
- `npm ls hono --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.
- 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-f6gv-hh8j-q8vq (OSV record GHSA-f6gv-hh8j-q8vq lists affected ranges: npm hono >=0 <3.11.7 (fixed))
- Verified: https://github.com/advisories/GHSA-f6gv-hh8j-q8vq (GitHub-reviewed advisory GHSA-f6gv-hh8j-q8vq lists affected ranges: npm hono >=0 <3.11.7)

Commands are suggestions: review each one before running it.