CVE-2026-44456: CWE-400: Uncontrolled Resource Consumption in honojs hono
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.16, bodyLimit() does not reliably enforce maxSize for requests without a usable Content-Length (e.g. Transfer-Encoding: chunked). Oversized requests can reach handlers and return 200 instead of 413. This vulnerability is fixed in 4.12.16.
AI Analysis
Technical Summary
The honojs hono framework versions before 4.12.16 contain an uncontrolled resource consumption vulnerability (CWE-400) due to improper enforcement of maxSize limits in the bodyLimit() function for requests without a usable Content-Length header. Specifically, requests using Transfer-Encoding: chunked can bypass size restrictions, potentially allowing oversized payloads to be processed by the application. This can lead to resource exhaustion or other impacts related to handling unexpectedly large requests. The issue is resolved in hono version 4.12.16.
Potential Impact
This vulnerability allows attackers to send oversized HTTP requests that bypass the intended maximum size checks, potentially causing resource exhaustion or degraded service availability. The affected versions respond with HTTP 200 OK instead of rejecting the request with HTTP 413 Payload Too Large, which may lead to unintended processing of large payloads. There is no indication of direct data confidentiality or integrity compromise. No known exploits are reported in the wild.
Mitigation Recommendations
Upgrade to hono version 4.12.16 or later, where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 4.12.16, applying this official fix is the recommended remediation. Patch status is not explicitly stated beyond this fix, but upgrading is the definitive mitigation.
CVE-2026-44456: CWE-400: Uncontrolled Resource Consumption in honojs hono
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.16, bodyLimit() does not reliably enforce maxSize for requests without a usable Content-Length (e.g. Transfer-Encoding: chunked). Oversized requests can reach handlers and return 200 instead of 413. This vulnerability is fixed in 4.12.16.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The honojs hono framework versions before 4.12.16 contain an uncontrolled resource consumption vulnerability (CWE-400) due to improper enforcement of maxSize limits in the bodyLimit() function for requests without a usable Content-Length header. Specifically, requests using Transfer-Encoding: chunked can bypass size restrictions, potentially allowing oversized payloads to be processed by the application. This can lead to resource exhaustion or other impacts related to handling unexpectedly large requests. The issue is resolved in hono version 4.12.16.
Potential Impact
This vulnerability allows attackers to send oversized HTTP requests that bypass the intended maximum size checks, potentially causing resource exhaustion or degraded service availability. The affected versions respond with HTTP 200 OK instead of rejecting the request with HTTP 413 Payload Too Large, which may lead to unintended processing of large payloads. There is no indication of direct data confidentiality or integrity compromise. No known exploits are reported in the wild.
Mitigation Recommendations
Upgrade to hono version 4.12.16 or later, where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 4.12.16, applying this official fix is the recommended remediation. Patch status is not explicitly stated beyond this fix, but upgrading is the definitive mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-06T15:49:25.193Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a049721cbff5d8610e00ed5
Added to database: 5/13/2026, 3:22:09 PM
Last enriched: 5/13/2026, 3:38:02 PM
Last updated: 5/13/2026, 4:22:59 PM
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.