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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-69207)

ID	Name	Product	Family	Type	Severity
465529	Echo: hono: security update to 4.12.34	Tenable Cloud Security	Echo Local Security Checks	Local	medium
465529	Echo: hono: security update to 4.12.34	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	medium
445613	SCA: security update for hono (GHSA-8j4g-w8fx-2239)	Tenable Cloud Security	SCA Checks	Local	medium
445613	SCA: security update for hono (GHSA-8j4g-w8fx-2239)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium

Detections

Analytics

CVE-2026-69207

medium

Tenable Plugins

medium

medium

medium

medium