High severity · published Sep 4, 2025
CVE-2025-58362
Hono contains a flaw in URL path parsing, potentially leading to path confusion
7.5
CVSS
0.6%
EPSS
No
On KEV
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Versions 4.8.0 through 4.9.5 contain a flaw in the getPath utility function which could allow path confusion and potential bypass of proxy-level ACLs (e.g. Nginx location blocks). 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 depending on the application and environment. 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, otherwise it may be moderate. This issue is fixed in version 4.9.6.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 46% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
HO
hono · honojs
>= 4.8.0, < 4.9.6 · source: vendor, NVD
Affected product
HO
hono
honojs
More from hono
9.8
CVE-2026-29045
Hono: Arbitrary file access via serveStatic vulnerability
8.1
CVE-2025-62610
Hono Improperly Authorizes JWT Audience Validation
7.5
CVE-2026-39408
Hono has a path traversal in toSSG() allows writing files outside the output directory
7.5
CVE-2026-27700
Hono is Vulnerable to Authentication Bypass by IP Spoofing in AWS Lambda ALB conninfo
7.1
CVE-2026-54290
Hono: CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard