CVE-2026-54288

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
6.5
EG Score
6.5(medium)
EPSS
1.2%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 23, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Patch available. Sources: github.
github Patch Available

Body Limit Middleware can be bypassed on AWS Lambda by understating `Content-Length` · Advisory · honojs/hono · GitHub

https://github.com/honojs/hono/security/advisories/GHSA-rv63-4mwf-qqc2

Vendor Advisories for CVE-2026-54288(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
hono—4.12.25—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 23:15 UTCEG score recompute
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 08:44 UTCEG score recompute
  5. 2026-07-05 02:31 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 09:21 UTCEG score recompute
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 06:45 UTCEG score recompute
  11. 2026-07-02 07:28 UTCEG score recompute
  12. 2026-07-01 15:07 UTCEPSS rescore
  13. 2026-07-01 08:13 UTCEG score recompute
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-30 08:58 UTCEG score recompute
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 09:44 UTCEG score recompute
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 10:26 UTCEG score recompute
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 11:05 UTCEG score recompute
  24. 2026-06-27 03:08 UTCEPSS rescore
  25. 2026-06-26 11:51 UTCEG score recompute
Show 13 more
  1. 2026-06-25 08:18 UTCEG score recompute
  2. 2026-06-24 14:05 UTCEPSS rescore
  3. 2026-06-24 09:04 UTCEG score recompute
  4. 2026-06-23 21:33 UTCEPSS rescore
  5. 2026-06-23 21:33 UTCEPSS rescore
  6. 2026-06-23 09:49 UTCEG score recompute
  7. 2026-06-22 10:32 UTCEG score recompute
  8. 2026-06-21 11:14 UTCEG score recompute
  9. 2026-06-20 11:54 UTCEG score recompute
  10. 2026-06-19 12:40 UTCEG score recompute
  11. 2026-06-18 13:23 UTCEG score recompute
  12. 2026-06-17 14:01 UTCEG score recompute
  13. 2026-06-16 14:46 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54288?
CVE-2026-54288 is a medium vulnerability published on June 16, 2026. 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…
When was CVE-2026-54288 disclosed?
CVE-2026-54288 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54288 actively exploited?
CVE-2026-54288 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54288?
CVE-2026-54288 has a CVSS v4.0 base score of 6.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-54288?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54288, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54288

Explore →

Is Your Infrastructure Affected by CVE-2026-54288?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs