Hono has Body Limit Middleware Bypass
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-400.
Summary
Hono is a Web application framework that provides support for any JavaScript runtime. In versions prior to 4.9.7, a flaw in the `bodyLimit` middleware could allow bypassing the configured request body size limit when conflicting HTTP headers were present. The middleware previously prioritized the `Content-Length` header even when a `Transfer-Encoding: chunked` header was also included. According to the HTTP specification, `Content-Length` must be ignored in such cases. This discrepancy could allow oversized request bodies to bypass the configured limit. Most standards-compliant runtimes and reverse proxies may reject such malformed requests with `400 Bad Request`, so the practical impact depends on the runtime and deployment environment. If body size limits are used as a safeguard against large or malicious requests, this flaw could allow attackers to send oversized request bodies. The primary risk is denial of service (DoS) due to excessive memory or CPU consumption when handling very large requests. The implementation has been updated to align with the HTTP specification, ensuring that `Transfer-Encoding` takes precedence over `Content-Length`. The issue is fixed in Hono v4.9.7, and all users should upgrade immediately.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| honojs | hono | before 4.9.7 | 4.9.7 | Patch available | CNA |
| — | hono (npm) | before 4.9.7 | 4.9.7 | Patch available | GHSA-92vj-g62v-jqhh |
- hono Vendorhonojs Affected before 4.9.7 Fixed in 4.9.7 Patch available CNA
- hono (npm) Vendor— Affected before 4.9.7 Fixed in 4.9.7 Patch available GHSA-92vj-g62v-jqhh
Remediation
- Fix · CNA hono (honojs) Fixed in 4.9.7
- Fix · GHSA-92vj-g62v-jqhh hono (npm) Fixed in 4.9.7 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2025-59139
- 2026-10-03 Alias added: GHSA-92vj-g62v-jqhh
References
More honojs Hono vulnerabilities
- TI-2024-21741 Hono vulnerable to Restricted Directory Traversal in serveStatic with deno CVSS 3.1MEDIUM 5.3
- TI-2024-32610 Hono vulnerable to bypass of CSRF Middleware by a request without Content-Type header. CVSS 3.1MEDIUM 5.9
- TI-2024-29381 Hono CSRF middleware can be bypassed using crafted Content-Type header CVSS 3.1MEDIUM 5.0
- TI-2026-23190 Hono: Arbitrary file access via serveStatic vulnerability CVSS 3.1CRITICAL 9.8
- TI-2026-22076 Hono is Vulnerable to Authentication Bypass by IP Spoofing in AWS Lambda ALB conninfo CVSS 3.1HIGH 8.2
- TI-2026-18334 JWT algorithm confusion in Hono JWK Auth Middleware when JWK lacks "alg" (untrusted header.alg fallback) CVSS 3.1HIGH 8.2
Sources
- CVE-2025-59139 · CVE Program
- CVE-2025-59139 · NVD
- FIRST EPSS
- GHSA-92vj-g62v-jqhh · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences