# CVE-2026-54288: Hono: Body Limit Middleware can be bypassed on AWS Lambda by understating `Content-Length`

> Attackers can bypass body size limits in Hono on AWS Lambda by spoofing Content-Length, potentially causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** ECHO-972b-f731-a0eb, GHSA-rv63-4mwf-qqc2, MINI-3gxf-929p-c85g, MINI-3rqp-fpc4-6cq4, MINI-7wxg-qr2m-774g, MINI-c6w5-h6hv-7h7w, MINI-cc67-m2pc-3h7x, MINI-f7qf-r786-vmxc, MINI-fwxm-mhpc-c24j, MINI-p82r-vmcm-3wm6, MINI-qhqq-mgc4-xw28, MINI-qmwv-9qr5-q2hq, MINI-rjv3-8mgw-h56g, MINI-wm87-v8pr-22f8, ROOT-APP-NPM-CVE-2026-54288

## What is CVE-2026-54288?

CVE-2026-54288 is a medium-severity vulnerability in honojs hono, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-54288?

2 open source packages ship an affected version, including hono.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hono` | npm | All versions | 4.12.25 |
| `hono` | npm | All versions | 4.12.25 |

## How do I fix CVE-2026-54288?

Upgrade hono to 4.12.25 or later.

## Is CVE-2026-54288 being exploited?

There is no known exploitation of CVE-2026-54288 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54288 and fix it if it is affected.

What it is: CVE-2026-54288 is a medium-severity vulnerability in honojs hono, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54288 in the wild and no public exploit code.

Affected packages and fixed versions:
- hono (npm): affected all versions; fixed in 4.12.25
- hono (npm): affected all versions; fixed in 4.12.25

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54288/ (Markdown: https://insights.sbomify.com/CVE-2026-54288/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54288
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54288
- OSV: https://osv.dev/vulnerability/CVE-2026-54288

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54288/
Summaries are generated and may contain mistakes; the official description above is the record.