Skip to main content
VulnerabilityPublished

CVE-2026-59897: 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.27 when convenient.

Data as of 20 Nov 2026, 17:35 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.27
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 8 Jul 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 20 Nov 2026.

What to do

Upgrade honojs hono to 4.12.27.

Affected software

ProductAffectedFixed in
honojshonoAffected
  • >=4.3.3 <4.12.27
Fixed in
  • 4.12.27

AI-suggested

A patch is available and the issue is fixed in Hono version 4.12.27. Users should upgrade to version 4.12.27 or later to resolve this vulnerability. Since this is a cloud service, the vendor manages remediation for the cloud-hosted service; users should verify with the vendor that the service is updated accordingly.

Description

Hono is a Web application framework that provides support for any JavaScript runtime. From 4.3.3 before 4.12.27, the AWS API Gateway v1 adapter can drop a distinct repeated request header value because it de-duplicates values using a substring comparison instead of an exact match, so middleware or application logic that depends on the complete X-Forwarded-For chain, rate limiting, audit logging, or proxy-chain validation can receive incomplete data. This issue is fixed in version 4.12.27.

References

Community reviews

Loading reviews…