CVE-2026-29087: CWE-863: Incorrect Authorization in honojs node-server
@hono/node-server allows running the Hono application on Node.js. Prior to version 1.19.10, when using @hono/node-server's static file serving together with route-based middleware protections (e.g. protecting /admin/*), inconsistent URL decoding can allow protected static resources to be accessed without authorization. In particular, paths containing encoded slashes (%2F) may be evaluated differently by routing/middleware matching versus static file path resolution, enabling a bypass where middleware does not run but the static file is still served. This issue has been patched in version 1.19.10.
AI Analysis
Technical Summary
The vulnerability CVE-2026-29087 affects the honojs node-server, a Node.js framework component used to run Hono applications. Prior to version 1.19.10, the server's static file serving mechanism and route-based middleware protections handle URL decoding inconsistently. Middleware protections, such as those restricting access to paths like /admin/*, rely on decoded URLs to enforce authorization. However, when URLs contain encoded slashes (%2F), the routing and middleware layers decode these differently than the static file path resolution layer. This discrepancy allows an attacker to craft URLs with encoded slashes that bypass middleware checks, resulting in unauthorized access to static files that should be protected. The vulnerability is classified under CWE-863 (Incorrect Authorization). It is remotely exploitable without authentication or user interaction, making it a significant risk. The flaw affects all versions of @hono/node-server before 1.19.10 and has been patched in that release. No known exploits are currently reported in the wild, but the ease of exploitation and impact on confidentiality justify a high severity rating with a CVSS score of 7.5.
Potential Impact
This vulnerability can lead to unauthorized disclosure of sensitive static files that are intended to be protected by route-based middleware. Organizations using affected versions of honojs node-server may inadvertently expose confidential information such as configuration files, administrative interfaces, or private assets. This exposure can facilitate further attacks, including reconnaissance and privilege escalation. Since the exploit requires no authentication or user interaction and can be performed remotely, the risk is elevated for publicly accessible web applications. The integrity and availability of the system are not directly impacted, but the confidentiality breach can have severe consequences, including data leakage, compliance violations, and reputational damage. The vulnerability is particularly critical for organizations hosting sensitive or regulated data on Hono-based Node.js applications.
Mitigation Recommendations
The primary mitigation is to upgrade all instances of @hono/node-server to version 1.19.10 or later, where the issue has been patched. Until the upgrade can be performed, organizations should implement strict input validation and URL normalization to prevent encoded slashes (%2F) from bypassing middleware protections. Additionally, configuring web application firewalls (WAFs) to detect and block suspicious encoded URL patterns can reduce exposure. Developers should audit their route-based middleware protections to ensure consistent URL decoding and authorization enforcement. Logging and monitoring access to static files, especially those under protected routes, can help detect exploitation attempts. Finally, security teams should review static file permissions and consider segregating sensitive static content to minimize risk.
Affected Countries
United States, Germany, United Kingdom, Japan, South Korea, France, Canada, Australia, Netherlands, India
CVE-2026-29087: CWE-863: Incorrect Authorization in honojs node-server
Description
@hono/node-server allows running the Hono application on Node.js. Prior to version 1.19.10, when using @hono/node-server's static file serving together with route-based middleware protections (e.g. protecting /admin/*), inconsistent URL decoding can allow protected static resources to be accessed without authorization. In particular, paths containing encoded slashes (%2F) may be evaluated differently by routing/middleware matching versus static file path resolution, enabling a bypass where middleware does not run but the static file is still served. This issue has been patched in version 1.19.10.
AI-Powered Analysis
Technical Analysis
The vulnerability CVE-2026-29087 affects the honojs node-server, a Node.js framework component used to run Hono applications. Prior to version 1.19.10, the server's static file serving mechanism and route-based middleware protections handle URL decoding inconsistently. Middleware protections, such as those restricting access to paths like /admin/*, rely on decoded URLs to enforce authorization. However, when URLs contain encoded slashes (%2F), the routing and middleware layers decode these differently than the static file path resolution layer. This discrepancy allows an attacker to craft URLs with encoded slashes that bypass middleware checks, resulting in unauthorized access to static files that should be protected. The vulnerability is classified under CWE-863 (Incorrect Authorization). It is remotely exploitable without authentication or user interaction, making it a significant risk. The flaw affects all versions of @hono/node-server before 1.19.10 and has been patched in that release. No known exploits are currently reported in the wild, but the ease of exploitation and impact on confidentiality justify a high severity rating with a CVSS score of 7.5.
Potential Impact
This vulnerability can lead to unauthorized disclosure of sensitive static files that are intended to be protected by route-based middleware. Organizations using affected versions of honojs node-server may inadvertently expose confidential information such as configuration files, administrative interfaces, or private assets. This exposure can facilitate further attacks, including reconnaissance and privilege escalation. Since the exploit requires no authentication or user interaction and can be performed remotely, the risk is elevated for publicly accessible web applications. The integrity and availability of the system are not directly impacted, but the confidentiality breach can have severe consequences, including data leakage, compliance violations, and reputational damage. The vulnerability is particularly critical for organizations hosting sensitive or regulated data on Hono-based Node.js applications.
Mitigation Recommendations
The primary mitigation is to upgrade all instances of @hono/node-server to version 1.19.10 or later, where the issue has been patched. Until the upgrade can be performed, organizations should implement strict input validation and URL normalization to prevent encoded slashes (%2F) from bypassing middleware protections. Additionally, configuring web application firewalls (WAFs) to detect and block suspicious encoded URL patterns can reduce exposure. Developers should audit their route-based middleware protections to ensure consistent URL decoding and authorization enforcement. Logging and monitoring access to static files, especially those under protected routes, can help detect exploitation attempts. Finally, security teams should review static file permissions and consider segregating sensitive static content to minimize risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-03T20:51:43.484Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69ab0f59c48b3f10ffb6232b
Added to database: 3/6/2026, 5:31:05 PM
Last enriched: 3/6/2026, 5:45:32 PM
Last updated: 3/7/2026, 7:36:48 AM
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.