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.7%, top 51% of all CVEs by exploit prediction. 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: 1%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 10, 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 rangeFixed inDependents
hono—4.12.34—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 28× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-19 18:57 UTCEG score recompute
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 18:19 UTCEG score recompute
  5. 2026-08-18 13:49 UTCEPSS rescore
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-17 16:02 UTCEG score recompute
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 15:49 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 02:15 UTCEPSS rescore
  13. 2026-08-15 15:36 UTCEG score recompute
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 15:22 UTCEG score recompute
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 14:56 UTCEG score recompute
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-11 14:43 UTCEG score recompute
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-10 14:30 UTCEG score recompute
  22. 2026-08-10 14:06 UTCEG score recompute
  23. 2026-08-09 21:58 UTCEG score recompute
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-08 21:45 UTCEG score recompute
Show 3 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-07 21:32 UTCEG score recompute
  3. 2026-08-03 21:07 UTCEG score recompute

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 in the National Vulnerability Database on August 3, 2026, with the most recent update on August 10, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 51.4% of all scored CVEs.
What is the CVSS score of CVE-2026-69207?
CVE-2026-69207 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-69207?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69207, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs