Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.34, the built-in CORS middleware, hono/cors, is vulnerable to a regular expression denial of service (ReDoS). During a preflight OPTIONS request, the middleware parses the attacker-controlled Access-Control-Request-Headers header using a whitespace-tolerant regular expression whose backtracking makes its running time quadratic in the input length. Because the header value is bounded only by the deployment's maximum HTTP header size, a single preflight carrying a long run of whitespace can consume seconds of CPU and block request processing. On runtimes that share one execution thread across requests, this stalls concurrent requests as well, and repeated requests can render the service unresponsive. This affects the default configuration, since the vulnerable path is reached whenever cors() is used with an unset or empty allowHeaders. Applications that set a non-empty allowHeaders are not affected. This issue is fixed in version 4.12.34.
Published: 2026-08-07
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a Regular Expression Denial of Service (ReDoS) in the built‑in CORS middleware of the Hono web application framework. During a preflight OPTIONS request the middleware parses the attacker‑controlled Access‑Control‑Request‑Headers header with a whitespace‑tolerant regular expression. Because the regex backtracks, the running time grows quadratically with the size of the header value. Large requests consisting of many whitespace characters can consume seconds of CPU, stall request processing, and on single‑threaded runtimes even block concurrent requests, potentially rendering the application unresponsive. The flaw is a CWE‑1333 weakness.

Affected Systems

All deployments of Hono version 4.12.33 and earlier are affected. The issue occurs whenever the cors() middleware is invoked with an unset or empty allowHeaders configuration. In contrast, applications that explicitly set a non‑empty allowHeaders list are not vulnerable. The problem is fixed in Hono release 4.12.34 and later.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate severity. No EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is remote: an attacker can provoke the vulnerability by issuing a crafted preflight OPTIONS request containing a very long Access‑Control‑Request‑Headers value. If the application is exposed to the Internet and executes without mitigation, repeated or large requests can consume CPU resources and cause denial of service. The vulnerability can be exploited without authentication and does not require privileged local access.

Generated by OpenCVE AI on August 7, 2026 at 22:23 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the application to Hono version 4.12.34 or later, which contains the fixed middleware implementation.
  • If upgrading is not immediately possible, configure the cors() middleware with an explicit allowHeaders parameter that lists the expected headers; this disables the vulnerable code path.
  • Reduce the maximum HTTP header size on the web server or reverse proxy to limit the potential input length that can be sent in a preflight request.

Generated by OpenCVE AI on August 7, 2026 at 22:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-8j4g-w8fx-2239 Hono: ReDoS in CORS middleware via Access-Control-Request-Headers
History

Fri, 07 Aug 2026 21:15:00 +0000

Type Values Removed Values Added
Description Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.34, the built-in CORS middleware, hono/cors, is vulnerable to a regular expression denial of service (ReDoS). During a preflight OPTIONS request, the middleware parses the attacker-controlled Access-Control-Request-Headers header using a whitespace-tolerant regular expression whose backtracking makes its running time quadratic in the input length. Because the header value is bounded only by the deployment's maximum HTTP header size, a single preflight carrying a long run of whitespace can consume seconds of CPU and block request processing. On runtimes that share one execution thread across requests, this stalls concurrent requests as well, and repeated requests can render the service unresponsive. This affects the default configuration, since the vulnerable path is reached whenever cors() is used with an unset or empty allowHeaders. Applications that set a non-empty allowHeaders are not affected. This issue is fixed in version 4.12.34.
Title Hono: ReDoS in CORS middleware via Access-Control-Request-Headers
Weaknesses CWE-1333
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-07T20:51:04.300Z

Reserved: 2026-08-03T16:57:50.124Z

Link: CVE-2026-69207

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-07T22:30:03Z

Weaknesses
  • CWE-1333

    Inefficient Regular Expression Complexity