CVE-2026-69207
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Exploit Intelligence
Moderate risk: more likely to be exploited than 48% of all known CVEs.
References
Related Vulnerabilities
Other CWE-1333 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-3364 | High | 7.5 | 44% | - | Fix |
| CVE-2024-8124 | High | 7.5 | 40% | - | Fix |
| CVE-2024-25126 | Medium | 5.3 | 35% | - | Fix |
| CVE-2024-2651 | Medium | 6.5 | 33% | - | Fix |
| CVE-2021-32837 | High | 7.5 | 29% | - | Fix |
| CVE-2024-2829 | High | 7.5 | 26% | - | Fix |
Common questions
How do I fix CVE-2026-69207?
No published fix for CVE-2026-69207 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-69207 being actively exploited?
Not that we know of. CVE-2026-69207 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.65% is the estimated probability that it will be exploited in the next 30 days. That is higher than 48% of all scored CVEs.
How severe is CVE-2026-69207?
CVE-2026-69207 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-69207
Markdown
[](https://tridentstack.com/cve/CVE-2026-69207)HTML
<a href="https://tridentstack.com/cve/CVE-2026-69207"><img src="https://tridentstack.com/cve/badge/CVE-2026-69207.svg" alt="CVE-2026-69207"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-10.