Skip to main content
VulnerabilityPublished

CVE-2026-54289: honojs hono · Use of Less Trusted Source

Affects honojs honoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium : upgrade to 4.12.25 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.12.25
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade honojs hono to 4.12.25.

Affected software

ProductAffectedFixed in
honojshonoAffected
  • <4.12.25
Fixed in
  • 4.12.25

AI-suggested

A fix is available in hono version 4.12.25. Users should upgrade to version 4.12.25 or later to resolve this issue. Since this is a cloud-hosted service scenario (AWS Lambda@Edge), the vendor manages remediation for the cloud environment. Check the vendor advisory for confirmation and apply the official patch accordingly.

Description

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.

References

Community reviews

Loading reviews…