CVE-2026-47676

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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, nvd
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 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.21, app.mount() strips the mount prefix from the incoming request path using the raw URL pathname, while route matching is performed against the percent-decoded path. This inconsistency causes the prefix to be stripped at the wrong position when the path contains percent-encoded multi-byte characters, resulting in the mounted sub-application receiving an incorrect path. This vulnerability is fixed in 4.12.21.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
17.4%
KEV
Not listed

Published

May 28, 2026

Last Modified

May 29, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
Patch available. Sources: github.
github Patch Available

app.mount() strips mount prefix using undecoded path, causing incorrect routing for percent-encoded paths · Advisory · honojs/hono · GitHub

https://github.com/honojs/hono/security/advisories/GHSA-2gcr-mfcq-wcc3

Vendor Advisories for CVE-2026-47676(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
hono4.12.21

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-47676?
CVE-2026-47676 is a medium vulnerability published on May 28, 2026. Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, app.mount() strips the mount prefix from the incoming request path using the raw URL pathname, while route matching is performed against the percent-decoded path. This inconsistency causes the…
When was CVE-2026-47676 disclosed?
CVE-2026-47676 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47676 actively exploited?
CVE-2026-47676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47676?
CVE-2026-47676 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-47676?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47676, 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-47676

Explore →

Is Your Infrastructure Affected by CVE-2026-47676?

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