Hono's flaw in URL path parsing could cause path confusion

Exploitation

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

CVSS

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

EPSS

• CVE-2025-58362: 0.55% estimated exploitation activity in the next 30 days; percentile 46.24 (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.

Summary A flaw in the getPath utility function could allow path confusion and potential bypass of proxy-level ACLs (e.g. Nginx location blocks). Details The original implementation relied on fixed character offsets when parsing request URLs. Under certain malformed absolute-form Request-URIs, this could lead to incorrect path extraction. Most standards-compliant runtimes and reverse proxies reject such malformed requests with a 400 Bad Request, so the impact depends on the application and environment. Impact If proxy ACLs are used to protect sensitive endpoints such as /admin, this flaw could have allowed unauthorized access. The confidentiality impact depends on what data is exposed: if sensitive administrative data is exposed, the impact may be High (CVSS 7.5); otherwise it may be Medium (CVSS 5.3). Resolution The implementation has been updated to correctly locate the first slash after "://", preventing such path confusion.

Published by the source

3 Sep 2025, 21:30 UTC

Last modified by the source

5 Sep 2025, 16:11 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9hp6-4448-45g2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9hp6-4448-45g2

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

# Patch Next advisory brief: CVE-2025-58362

Advisory: Hono's flaw in URL path parsing could cause path confusion
IDs: CVE-2025-58362, GHSA-9hp6-4448-45g2
Record: https://patchnext.com/advisories/cve-2025-58362 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hono 4.9.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm hono: affected >= 4.8.0, < 4.9.6; fixed in 4.9.6

## 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-9hp6-4448-45g2 (OSV record GHSA-9hp6-4448-45g2 lists affected ranges: npm hono >=4.8.0 <4.9.6 (fixed))
- Verified: https://github.com/advisories/GHSA-9hp6-4448-45g2 (GitHub-reviewed advisory GHSA-9hp6-4448-45g2 lists affected ranges: npm hono >=4.8.0 <4.9.6)

Commands are suggestions: review each one before running it.