CVE-2026-54289

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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: epss, secondary
4.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.8Exploit: 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, on AWS Lambda@Edge, CloudFront delivers a request header that appears more than once as several separate entries. The adapter writes each value with Headers.set instead of Headers.append, so every value overwrites the previous one and only the last reaches the application. Repeated request headers such as X-Forwarded-For, Forwarded, and Via are silently truncated to a single value. Request middleware sees only the last value of a repeated header instead of the full chain. For applications that base access control on the X-Forwarded-For chain, this can weaken or alter that decision; for auditing, hop history is lost. This vulnerability is fixed in 4.12.25.

CVSS v3
4.8
EG Score
4.8(medium)
EPSS
1.7%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 22, 2026

Advisory Details (1)

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

Lambda@Edge adapter keeps only the last value of a repeated request header, dropping the rest · Advisory · honojs/hono · GitHub

https://github.com/honojs/hono/security/advisories/GHSA-wgpf-jwqj-8h8p

Vendor Advisories for CVE-2026-54289(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 14× in last 7d / 35× 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 13:31 UTCEG score recompute
  5. 2026-07-05 02:31 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 13:40 UTCEG score recompute
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 13:49 UTCEG score recompute
  11. 2026-07-02 12:44 UTCEG score recompute
  12. 2026-07-01 12:54 UTCEG score recompute
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-30 13:04 UTCEG score recompute
  15. 2026-06-29 13:14 UTCEG score recompute
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 13:24 UTCEG score recompute
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 13:35 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 13:45 UTCEG score recompute
  23. 2026-06-25 13:56 UTCEG score recompute
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 14:06 UTCEG score recompute
Show 10 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-23 14:17 UTCEG score recompute
  4. 2026-06-22 14:05 UTCEG score recompute
  5. 2026-06-21 14:13 UTCEG score recompute
  6. 2026-06-20 14:24 UTCEG score recompute
  7. 2026-06-19 14:28 UTCEG score recompute
  8. 2026-06-18 14:38 UTCEG score recompute
  9. 2026-06-17 14:35 UTCEG score recompute
  10. 2026-06-16 14:46 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54289?
CVE-2026-54289 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, on AWS Lambda@Edge, CloudFront delivers a request header that appears more than once as several separate entries. The adapter writes each value with Headers.set instead of Headers.append, so…
When was CVE-2026-54289 disclosed?
CVE-2026-54289 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54289 actively exploited?
CVE-2026-54289 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54289?
CVE-2026-54289 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-54289?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54289, 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-54289

Explore →

Is Your Infrastructure Affected by CVE-2026-54289?

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

Start Free Scan →Browse All CVEs