Hono is a Web application framework that provides support for any JavaScript runtime. From 4.12.12 until 4.13.5, the fix released for CVE-2026-39408 does not cover every traversal sequence, and toSSG() can still write files outside the configured output directory when a route parameter contains consecutive parent-directory segments. Static site generation builds each output path from the route path and values supplied through ssgParams, then verifies that the result stays inside the output directory using the same normalization routine that built the path. That routine does not fully collapse runs of consecutive parent-directory segments, allowing a path that the check accepts to resolve outside the output directory, and the check also treats output directories that differ in how they are rooted as equivalent. This arises when an application generates a static site from route parameter values it does not fully control, such as slugs from a CMS, API, or user submission. An untrusted ssgParams value can create or overwrite files elsewhere in the build environment and alter generated artifacts or deployment output. The vulnerability affects build-time static site generation only; request-time routing and applications with entirely developer-controlled ssgParams values are not affected. This issue is fixed in version 4.13.5.
CVE-2026-84365
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
September 1, 2026
Last Modified
September 9, 2026
Advisory Details (3)
Auto-updated Sep 1, 2026v4.13.5
Patch available: honojs/hono v4.13.5
https://github.com/honojs/hono/releases/tag/v4.13.5commit 3a67f7f3997e (honojs/hono)
Patch available: honojs/hono v4.13.5 (contains commit 3a67f7f3997e)
https://github.com/honojs/hono/commit/3a67f7f3997e1437d108f7bcba2dbcee2df69221Incomplete fix for CVE-2026-39408: `toSSG()` still writes files outside the output directory · Advisory · honojs/hono · GitHub
https://github.com/honojs/hono/security/advisories/GHSA-gqvv-2mrq-wpjvVendor Advisories for CVE-2026-84365(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| hono | — | 4.13.5 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 32× 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.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 15:12 UTCEG score recompute
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 13:02 UTCEG score recompute
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 10:44 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 08:33 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 06:23 UTCEG score recompute
- 2026-09-13 04:13 UTCEG score recompute
- 2026-09-12 02:03 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 23:53 UTCEG score recompute
- 2026-09-09 14:21 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 12:11 UTCEG score recompute
- 2026-09-07 09:57 UTCEG score recompute
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 07:45 UTCEG score recompute
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 05:33 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescore
Show 7 moreShow fewer
- 2026-09-04 03:23 UTCEG score recompute
- 2026-09-04 02:34 UTCEG score recompute
- 2026-09-02 23:38 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 21:27 UTCEG score recompute
- 2026-09-01 20:34 UTCEG score recompute
- 2026-09-01 20:32 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-84365?
When was CVE-2026-84365 disclosed?
Is CVE-2026-84365 actively exploited?
What is the CVSS score of CVE-2026-84365?
How do I remediate CVE-2026-84365?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84365
Is Your Infrastructure Affected by CVE-2026-84365?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.