CVE-2025-58362

7.5

Hono · Hono

Hono versions 4.8.0 through 4.9.5 contain a path confusion flaw in the getPath utility, potentially allowing unauthenticated attackers to bypass proxy-level access control lists.

Executive summary

A path confusion vulnerability in the Hono web framework allows unauthenticated attackers to bypass security restrictions, posing a significant risk to protected administrative endpoints.

Vulnerability

The flaw exists within the getPath utility function, which incorrectly parses malformed absolute-form request URIs due to reliance on fixed character offsets. An unauthenticated attacker can exploit this to bypass proxy-level ACLs, such as those configured in Nginx to protect sensitive administrative paths.

Business impact

The ability to bypass proxy-level access controls can lead to the unauthorized exposure of sensitive data or administrative interfaces. With a CVSS score of 7.5, this high-severity vulnerability represents a substantial risk to organizational confidentiality, particularly if protected endpoints contain private user data or elevated configuration settings.

Remediation

Immediate Action: Update Hono to version 4.9.6 or later to incorporate the corrected path parsing logic.

Proactive Monitoring: Review web server and proxy access logs for unusual patterns, specifically looking for requests that target sensitive directories using malformed or non-standard URI formats.

Compensating Controls: Ensure that access control is enforced at the application level rather than relying solely on upstream proxy configuration, and implement strict input validation for all incoming request paths.

Exploitation status

Public Exploit Available: No — exploit_available (false).

Analyst recommendation

Given the potential for unauthorized access to administrative resources, organizations currently using Hono versions 4.8.0 through 4.9.5 must prioritize upgrading to version 4.9.6. Failure to patch leaves applications vulnerable to simple URI-based bypass techniques that could result in significant data exposure.

More Hono CVEs

History

  1. Disclosed CVE record published
  2. Published in the daily brief high section
  3. Published in the daily brief high section
  4. Analyst report written
  5. Fix documented version 4.9.6 per OSV.dev

Sources