CVE-2026-54288: CWE-345: Insufficient Verification of Data Authenticity in honojs hono
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.25, the Body Limit Middleware trusts the request's Content-Length header to decide whether a body is within the limit. On AWS Lambda (API Gateway v1/v2, ALB, VPC Lattice, and Lambda@Edge) the body is delivered fully buffered and the adapter builds the request with the client-declared Content-Length, which need not match the actual payload. A client can declare a tiny Content-Length while sending a much larger body, slipping past the limit. This vulnerability is fixed in 4.12.25.
AI Analysis
Technical Summary
CVE-2026-54288 is a vulnerability in the honojs hono web framework affecting versions prior to 4.12.25. The Body Limit Middleware trusts the Content-Length header to determine if the request body size is within limits. However, on AWS Lambda platforms (including API Gateway v1/v2, ALB, VPC Lattice, and Lambda@Edge), the body is fully buffered and the adapter constructs the request using the client-declared Content-Length, which may not match the actual payload size. This discrepancy allows an attacker to declare a smaller Content-Length header while sending a larger body, bypassing the middleware's size checks. The vulnerability is addressed in hono version 4.12.25.
Potential Impact
An attacker can bypass the body size limit enforcement by sending a request with a falsely small Content-Length header but a larger actual payload. This may lead to processing of unexpectedly large request bodies, potentially causing resource exhaustion or other issues related to handling oversized payloads. The confidentiality and integrity impact is limited (low), and availability is not affected.
Mitigation Recommendations
A patch is available in hono version 4.12.25 that fixes this vulnerability by properly verifying the actual payload size rather than relying solely on the Content-Length header. Users should upgrade to version 4.12.25 or later. Since this is a cloud-hosted service environment (AWS Lambda), the vendor manages remediation for the cloud-hosted service; however, for self-hosted deployments, upgrading is required. No additional mitigations are specified.
CVE-2026-54288: CWE-345: Insufficient Verification of Data Authenticity in honojs hono
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.25, the Body Limit Middleware trusts the request's Content-Length header to decide whether a body is within the limit. On AWS Lambda (API Gateway v1/v2, ALB, VPC Lattice, and Lambda@Edge) the body is delivered fully buffered and the adapter builds the request with the client-declared Content-Length, which need not match the actual payload. A client can declare a tiny Content-Length while sending a much larger body, slipping past the limit. This vulnerability is fixed in 4.12.25.
CVSS v3.1
Score 6.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-54288 is a vulnerability in the honojs hono web framework affecting versions prior to 4.12.25. The Body Limit Middleware trusts the Content-Length header to determine if the request body size is within limits. However, on AWS Lambda platforms (including API Gateway v1/v2, ALB, VPC Lattice, and Lambda@Edge), the body is fully buffered and the adapter constructs the request using the client-declared Content-Length, which may not match the actual payload size. This discrepancy allows an attacker to declare a smaller Content-Length header while sending a larger body, bypassing the middleware's size checks. The vulnerability is addressed in hono version 4.12.25.
Potential Impact
An attacker can bypass the body size limit enforcement by sending a request with a falsely small Content-Length header but a larger actual payload. This may lead to processing of unexpectedly large request bodies, potentially causing resource exhaustion or other issues related to handling oversized payloads. The confidentiality and integrity impact is limited (low), and availability is not affected.
Mitigation Recommendations
A patch is available in hono version 4.12.25 that fixes this vulnerability by properly verifying the actual payload size rather than relying solely on the Content-Length header. Users should upgrade to version 4.12.25 or later. Since this is a cloud-hosted service environment (AWS Lambda), the vendor manages remediation for the cloud-hosted service; however, for self-hosted deployments, upgrading is required. No additional mitigations are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-12T17:46:37.293Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a398861eed863c81e5021c8
Added to database: 06/22/2026, 19:09:21 UTC
Last enriched: 06/29/2026, 21:51:59 UTC
Last updated: 08/06/2026, 12:41:11 UTC
Views: 54
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.