Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Hono app with ip-restriction middleware
-
DeliveryDetermine target IPv6 deny/allow rule
-
ExploitCraft non-canonical IPv6 form of restricted address
-
ExecutionSubmit HTTP request with alternate IPv6 representation
-
PersistMiddleware skips rule match silently
-
ImpactGain access to restricted endpoint
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Incorrect input validation
|
| Exploitation Conditions | Exploitation requires that the target Hono application uses the hono/ip-restriction middleware with at least one IPv6 address configured in its deny or allow rule set. The attacker must control or spoof a source IPv6 address that is subject to a configured restriction rule, and must connect using a non-canonical representation of that address - specifically a compressed form, explicit-zero form, or hex-notation IPv4-mapped form - that the middleware fails to normalize before comparison. The bypass does not apply to pure IPv4 rule sets, and requires that the attacker's IPv6 address be expressible in an alternate representation not handled by the partial normalization logic. Exploitation is further limited by the context of what the IP restriction is protecting: if the restricted endpoint independently requires authentication or other access controls, bypassing the IP filter alone does not yield full access. CVSS confirms no authentication is required and no user interaction is needed (PR:N/UI:N) for the network-layer bypass itself. |
| Impact | The CVSS 5.3 Medium score (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) reflects a network-accessible, unauthenticated, low-complexity bypass with only low integrity impact - the attack surface is wide but the direct CVSS-scored impact is narrow. No EPSS data was provided in the input and cannot be independently quantified here. This CVE is not listed in CISA KEV, and no public exploit code has been identified at time of analysis, indicating no confirmed widespread or active exploitation. The practical real-world risk is highly context-dependent: applications using ip-restriction as a sole or primary access control mechanism on sensitive or administrative endpoints face meaningful exposure, as the bypass is trivially achieved by reformatting an IPv6 address. If protected resources have independent authentication or additional access controls, the effective impact of bypassing the IP filter is substantially reduced. The low integrity-only CVSS impact (I:L, C:N, A:N) accurately captures the narrow technical scope - no data is directly exfiltrated and no availability is disrupted - but understates risk in deployments where IP allowlisting is the primary security boundary. |
| Exploit ScenarioDerived | An attacker whose IPv6 address has been added to a deny list in the Hono ip-restriction configuration connects to the application using a non-canonical representation of their blocked address - for example, substituting compressed notation with an explicit-zero form or using a hex-encoded IPv4-mapped IPv6 address. The middleware compares the submitted string against the partially normalized rule entry, finds no match, silently skips enforcement, and grants the attacker access to the restricted endpoint. No public exploit code is known, but the technique requires only standard knowledge of IPv6 address representation equivalence, making it trivially reproducible. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 28, 2026
IP restriction bypass in Hono's ip-restriction middleware (hono/ip-restriction) prior to version 4.12.21 allows unauthenticated remote attackers to circumvent configured deny and allow rules by submitting non-canonical IPv6 representations of restricted addresses. String equality comparison applied after only partial normalization means that compressed, explicit-zero, or hex-notation IPv4-mapped IPv6 forms of a listed address silently fail to match the normalized rule entry, causing enforcement to be skipped entirely. No public exploit has been identified at time of analysis, but the bypass requires only trivial reformatting of a standard IPv6 address, making it practically low-effort for any attacker aware of the flaw.
RemediationAI
Upgrade Hono to version 4.12.21 or later, which resolves the incomplete IPv6 normalization in the ip-restriction middleware; this is the vendor-released patch confirmed by the GitHub security advisory at https://github.com/honojs/hono/security/advisories/GHSA-xrhx-7g5j-rcj5. If an immediate upgrade is not feasible, implement IP restriction at the infrastructure layer - such as a reverse proxy (nginx, Caddy), CDN edge rules, or host-based firewall - rather than relying solely on the application-level middleware, as infrastructure-layer controls typically perform full canonicalization and eliminate the normalization gap entirely. As a partial interim measure, ensure all configured deny and allow rule entries use fully expanded canonical IPv6 notation, which reduces (but does not eliminate) the attack surface since the application still does not normalize incoming addresses before comparison. Do not treat the application-level hono/ip-restriction middleware as a reliable security boundary in isolation until the upgrade to 4.12.21 is applied.
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 is a lightweight Web application framework supporting all major JavaScript runtimes including Cloudflare Workers, Deno, Bun, and Node.js. Its hono/ip-restriction middleware evaluates incoming client IP addresses against configured allow/deny rule sets using string equality after partial normalization. IPv6 has numerous canonically equivalent representations: compressed forms (e.g., ::1 vs 0:0:0:0:0:0:0:1), explicit-zero forms, and IPv4-mapped addresses in hex notation (e.g., ::ffff:c0a8:0101 vs ::ffff:192.168.1.1). Because the middleware's normalization was incomplete, these alternate forms did not match normalized rule entries stored internally, creating a systematic bypass class. CWE-185 (Incorrect Regular Expression) broadly covers flawed pattern or string-matching logic; in this case the root cause is that the comparison logic lacked a full canonicalization step over the IPv6 address space before comparison. The affected CPE is cpe:2.3:a:honojs:hono:*:*:*:*:*:*:*:* covering all Hono versions prior to 4.12.21.
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
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the ip-restriction middleware (hono/ip-restriction) compares incoming IP addresses against configured deny and allow rules using string equality after partial normalization. Non-canonical IPv6 representations of an address already listed in a static rule - such as compressed forms, explicit-zero forms, or hex-notation IPv4-mapped addresses - do not match the normalized rule entry, causing the rule to be silently skipped. This vulnerability is fixed in 4.12.21.
Blast Radius
ecosystem impact- 8 npm packages depend on hono (8 direct, 0 indirect)
Ecosystem-wide dependent count for version 4.12.21.
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-32926
GHSA-xrhx-7g5j-rcj5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB