Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify target using Hono AWS API Gateway v1 adapter
-
DeliveryCraft request with overlapping X-Forwarded-For values triggering substring match
-
ExploitAdapter drops distinct header entry during de-duplication
-
ExecutionSecurity middleware receives truncated header chain
-
ImpactIP-based rate limit or blocklist control bypassed
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V6 - Authentication IP-independent access control
|
| Exploitation Conditions | Exploitation requires that the application is deployed on AWS Lambda behind an AWS API Gateway v1 (REST API) endpoint - not API Gateway v2 (HTTP API). The Hono AWS API Gateway v1 adapter must be actively used as the runtime adapter. The security impact only materializes when middleware or application logic downstream of the adapter relies on the completeness or distinctness of repeated request header values such as X-Forwarded-For for rate limiting, audit logging, IP allowlisting, or proxy-chain validation. The attacker must control or influence the values of repeated headers in the incoming request, which typically means the attacker is either the direct client or able to inject headers through an upstream proxy. Exploitation is limited by AC:H - the crafted values must satisfy the substring overlap condition, which requires knowledge of existing header values in the chain. No authentication is required (PR:N). Applications not using security controls that depend on complete repeated header values are not at meaningful risk even if running the affected version. |
| Impact | The NVD CVSS 3.1 score of 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N) accurately reflects a medium-severity, network-accessible issue with elevated attack complexity. AC:H is appropriate because the attacker must craft request headers where one IP or token value is a substring of another, which requires knowing or guessing values already in the chain - a non-trivial precondition. The impact is indirect: no direct data exfiltration or command execution, but integrity (I:L) and confidentiality (C:L) are plausible via bypass of IP-based rate limiting, audit log tampering, or proxy-trust circumvention. No EPSS data was provided in the input, so exploitation probability cannot be quantitatively assessed. No KEV listing exists, and no POC code has been identified at time of analysis. The realistic risk priority is moderate and context-dependent: organizations using Hono with the AWS API Gateway v1 adapter in security-sensitive workflows (rate limiting, fraud detection, audit compliance) should treat this as a priority patch; those using the v2 adapter or not relying on header-based security controls face minimal practical risk. |
| Exploit ScenarioDerived | An attacker sends a crafted HTTP request through an AWS API Gateway v1 endpoint with X-Forwarded-For values engineered so that one IP address is a substring of another (for example, '192.168.1.1' alongside '192.168.1.10'). The Hono adapter's substring de-duplication silently drops one entry, causing an upstream rate-limiting middleware to see a shorter chain and potentially misidentify the originating IP, allowing the attacker to exceed rate limits or evade IP-based blocklisting. No public POC has been identified, but the logic flaw is straightforward enough to reproduce from the advisory description alone. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 08, 2026
Header de-duplication logic in Hono's AWS API Gateway v1 adapter silently drops distinct repeated header values because it uses substring comparison rather than exact string equality, meaning a value like '10.0.0.1' would incorrectly suppress '10.0.0.10'. Middleware or application logic relying on a complete X-Forwarded-For chain, rate limiting counters, audit trail integrity, or proxy-chain trust validation receives a truncated view of the request. Affected versions span 4.3.3 through 4.12.26; no public exploit identified at time of analysis, though the GitHub advisory confirms the issue and a fix is released in v4.12.27.
RemediationAI
Vendor-released patch: v4.12.27. Upgrade to Hono v4.12.27 or later using your package manager (e.g., npm install hono@4.12.27 or equivalent). The fix is confirmed via the GitHub release at https://github.com/honojs/hono/releases/tag/v4.12.27 and the underlying commit at https://github.com/honojs/hono/commit/aa921770d09bc35970362d5a2630a878f6d982fd. If an immediate upgrade is not feasible, a compensating control is to move header-dependent security logic (rate limiting, IP allowlisting, audit logging) upstream into the AWS API Gateway itself using request validators, WAF rules, or Lambda authorizers - this avoids dependence on the adapter's header normalization. Note that this workaround adds operational complexity and does not fix the underlying data integrity issue. Applications that do not use the AWS API Gateway v1 adapter or do not rely on repeated header value completeness for security decisions are not at meaningful risk and can defer patching to their normal cycle.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Hono (honojs/hono, CPE cpe:2.3:a:honojs:hono:*:*:*:*:*:*:*:*) is a lightweight, multi-runtime JavaScript web framework used across Cloudflare Workers, Deno, Bun, Node.js, and AWS Lambda runtimes. The AWS API Gateway v1 adapter is responsible for translating API Gateway event payloads - where multi-value headers are represented as arrays - into standard HTTP request objects. The de-duplication step that collapses repeated header values is implemented using substring matching (e.g., String.includes or equivalent) rather than strict equality, violating the RFC 7230 requirement that multi-value header fields be treated as distinct comma-separated entries. CWE-348 (Use of Less Trusted Source) captures the root cause: the adapter effectively discards legitimate header data, causing downstream logic to operate on a less complete - and therefore less trustworthy - representation of the original request. The affected code path is specific to the v1 (REST API) adapter; whether the v2 (HTTP API) adapter shares this logic is not confirmed from available data.
Know when Hono gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Network-reachable via API Gateway (AV:N) but requires crafted substring-overlapping header values and v1 adapter deployment (AC:H); no auth needed; limited C/I via security-control bypass; no availability impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
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.
Blast Radius
ecosystem impact- 1 npm packages depend on hono (1 direct, 0 indirect)
Ecosystem-wide dependent count for version 4.3.3.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Improper authorization in Hono's JWT Auth Middleware (hono/jwt in the npm package 'hono', versions 1.1.0 through 4.10.1)
The adapter @hono/node-server allows you to run your Hono application on Node.js. Rated high severity (CVSS 7.5), this v
Hono, a web framework, prior to version 4.6.5 is vulnerable to bypass of cross-site request forgery (CSRF) middleware by
Quadratic-complexity denial of service in Hono's `languageDetector` middleware (versions 4.12.0-4.12.33) allows unauthen
Path prefix stripping in Hono's app.mount() API exposes mounted sub-applications to incorrect routing due to a raw-vs-de
Hono is a Web application framework that provides support for any JavaScript runtime. Rated medium severity (CVSS 5.3),
@hono/node-server is an adapter that allows users to run Hono applications on Node.js. Rated medium severity (CVSS 5.3),
Hono is a Web application framework that provides support for any JavaScript runtime. Rated medium severity (CVSS 5.0),
Cross-user HTML disclosure in Hono's server-side rendering affects all applications using hono/jsx with memo()-wrapped c
Hono is a web framework written in TypeScript. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploita
Hono is a Web application framework that provides support for any JavaScript runtime. [CVSS 8.2 HIGH]
Hono versions before 4.11.4 allow JWT algorithm confusion attacks through improper algorithm validation in the JWK/JWKS
EUVD-2026-42325
GHSA-xgm2-5f3f-mvvc
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB