CVE-2026-24398
Hono IPv4 address validation bypass in IP Restriction Middleware allows IP spoofing
Overview
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to version 4.11.7, IP Restriction Middleware in Hono is vulnerable to an IP address validation bypass. The IPV4_REGEX pattern and convertIPv4ToBinary function in src/utils/ipaddr.ts do not properly validate that IPv4 octet values are within the valid range of 0-255, allowing attackers to craft malformed IP addresses that bypass IP-based access controls. Version 4.11.7 contains a patch for the issue.
Source: OX vulnerability database
Severity
6.5 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Weakness: CWE-185
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| npm | hono | <4.11.7 | 4.11.7 |
Open a package to see all its vulnerabilities.
Operating systems · 7 fixes
chainguard 1 release · 4 packages
| Release | Package | Fixed in |
|---|---|---|
| hono | not affected | |
| librechat | 0.8.2-r1 | |
| langfuse-fips-3 | 3.152.0-r0 | |
| langfuse-3 | 3.153.0-r0 |
minimos 1 release · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| mcp-filesystem | 2026.6.16-r0 | |
| trigger-dev | 4.5.4-r0 |
wolfi 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| langfuse-3 | 3.153.0-r0 |
References
- github.com https://github.com/honojs/hono
- github.com https://github.com/honojs/hono/commit/edbf6eea8e6c26a3937518d4ed91d8666edeec37
- github.com https://github.com/honojs/hono/releases/tag/v4.11.7
- github.com https://github.com/honojs/hono/security/advisories/GHSA-r354-f388-2fhh
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2026-24398
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.