CVE-2026-69207

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 3, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 7, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v4.12.34

Patch available: honojs/hono v4.12.34

https://github.com/honojs/hono/releases/tag/v4.12.34
github_commit Patch Available

commit 93fc250d8b4d (honojs/hono)

Patch available: honojs/hono v4.12.34 (contains commit 93fc250d8b4d)

https://github.com/honojs/hono/commit/93fc250d8b4df58ea542cb945171de8013d5e6d5
github Patch Available

ReDoS in CORS middleware via Access-Control-Request-Headers · Advisory · honojs/hono · GitHub

https://github.com/honojs/hono/security/advisories/GHSA-8j4g-w8fx-2239

Vendor Advisories for CVE-2026-69207(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
hono—
  • every version up to 4.12.34: fixed in 4.12.34
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 06:17 UTCEG score recompute
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-02 17:56 UTCEPSS rescore
  5. 2026-10-02 10:17 UTCEG score recompute
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-10-01 02:32 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-29 06:36 UTCEG score recompute
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-27 18:14 UTCEG score recompute
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-25 04:45 UTCEG score recompute
  15. 2026-09-24 04:24 UTCEG score recompute
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 04:10 UTCEG score recompute
  18. 2026-09-22 03:53 UTCEG score recompute
  19. 2026-09-21 21:09 UTCEPSS rescore
  20. 2026-09-20 11:04 UTCEG score recompute
  21. 2026-09-19 08:00 UTCEG score recompute
  22. 2026-09-18 19:28 UTCEPSS rescore
  23. 2026-09-18 05:45 UTCEG score recompute
  24. 2026-09-17 05:31 UTCEG score recompute
  25. 2026-09-16 14:08 UTCEPSS rescore
Show 67 more
  1. 2026-09-16 05:18 UTCEG score recompute
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-14 01:12 UTCEG score recompute
  4. 2026-09-13 00:59 UTCEG score recompute
  5. 2026-09-12 00:25 UTCEG score recompute
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 09:37 UTCEPSS rescore
  8. 2026-09-10 22:54 UTCEG score recompute
  9. 2026-09-09 06:42 UTCEG score recompute
  10. 2026-09-08 22:01 UTCEPSS rescore
  11. 2026-09-07 18:47 UTCEG score recompute
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 10:48 UTCEG score recompute
  15. 2026-09-05 15:31 UTCEPSS rescore
  16. 2026-09-05 10:34 UTCEG score recompute
  17. 2026-09-04 10:16 UTCEG score recompute
  18. 2026-09-04 05:07 UTCEPSS rescore
  19. 2026-09-03 08:41 UTCEG score recompute
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 23:23 UTCEG score recompute
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-30 22:11 UTCEG score recompute
  25. 2026-08-30 19:17 UTCEPSS rescore
  26. 2026-08-30 01:22 UTCEPSS rescore
  27. 2026-08-29 21:57 UTCEG score recompute
  28. 2026-08-28 21:42 UTCEPSS rescore
  29. 2026-08-27 21:12 UTCEG score recompute
  30. 2026-08-26 20:59 UTCEG score recompute
  31. 2026-08-26 14:47 UTCEPSS rescore
  32. 2026-08-25 20:18 UTCEG score recompute
  33. 2026-08-25 13:49 UTCEPSS rescore
  34. 2026-08-24 20:05 UTCEG score recompute
  35. 2026-08-23 19:51 UTCEG score recompute
  36. 2026-08-23 00:19 UTCEPSS rescore
  37. 2026-08-22 19:38 UTCEG score recompute
  38. 2026-08-21 23:49 UTCEPSS rescore
  39. 2026-08-21 19:25 UTCEG score recompute
  40. 2026-08-20 22:56 UTCEPSS rescore
  41. 2026-08-19 18:57 UTCEG score recompute
  42. 2026-08-19 17:04 UTCEPSS rescore
  43. 2026-08-18 18:19 UTCEG score recompute
  44. 2026-08-18 13:49 UTCEPSS rescore
  45. 2026-08-18 13:49 UTCEPSS rescore
  46. 2026-08-17 16:02 UTCEG score recompute
  47. 2026-08-17 13:47 UTCEPSS rescore
  48. 2026-08-16 15:49 UTCEG score recompute
  49. 2026-08-16 14:56 UTCEPSS rescore
  50. 2026-08-16 14:56 UTCEPSS rescore
  51. 2026-08-16 02:15 UTCEPSS rescore
  52. 2026-08-15 15:36 UTCEG score recompute
  53. 2026-08-15 01:30 UTCEPSS rescore
  54. 2026-08-14 15:22 UTCEG score recompute
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-12 14:56 UTCEG score recompute
  57. 2026-08-12 13:51 UTCEPSS rescore
  58. 2026-08-11 14:43 UTCEG score recompute
  59. 2026-08-11 00:00 UTCEPSS rescore
  60. 2026-08-10 14:30 UTCEG score recompute
  61. 2026-08-10 14:06 UTCEG score recompute
  62. 2026-08-09 21:58 UTCEG score recompute
  63. 2026-08-09 13:47 UTCEPSS rescore
  64. 2026-08-08 21:45 UTCEG score recompute
  65. 2026-08-08 16:37 UTCEPSS rescore
  66. 2026-08-07 21:32 UTCEG score recompute
  67. 2026-08-03 21:07 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-69207?
CVE-2026-69207 is a medium vulnerability published on August 3, 2026. 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…
When was CVE-2026-69207 disclosed?
CVE-2026-69207 was first published on August 3, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69207 actively exploited?
CVE-2026-69207 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69207?
CVE-2026-69207 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69207?
A fix for CVE-2026-69207 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69207 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69207

Explore →

Is Your Infrastructure Affected by CVE-2026-69207?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs