CVE-2026-84363

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.9 from GitHub Security Advisory (severity: MODERATE) published 2026-09-08. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-69610 (ENISA EUVD) · GHSA-crvj-82cr-hjcx (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: 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.13.5, Hono's query helpers treat a question mark after a literal hash fragment as the start of a query string, so the application can read request parameters that browsers, new URL(), reverse proxies, filtering rules, parameter allow and deny lists, access logging, request validation, and other middleware do not observe. The Cache Middleware removes the fragment when building its cache key, allowing a response influenced by parameters inside the fragment to be stored under a key that omits those parameters and later served to other users. This can bypass filtering and auditing, poison cached responses, and enable stored cross-site scripting when an affected parameter is reflected into cached HTML without escaping. Exploitation requires a runtime and intermediary path that passes a literal hash character through to the request URL; Cloudflare Workers and intermediaries that strip fragments are not affected. This issue is fixed in version 4.13.5.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 1, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Sep 1, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub release Patch Available

v4.13.5

Patch available: honojs/hono v4.13.5

https://github.com/honojs/hono/releases/tag/v4.13.5
GitHub commit Patch Available

commit 9c28d724c5a7 (honojs/hono)

Patch available: honojs/hono v4.13.5 (contains commit 9c28d724c5a7)

https://github.com/honojs/hono/commit/9c28d724c5a7fb086ebaa812fdc1ad6e957c63bc
GitHub advisoryMentions a patch (unverified)

Query parser reads parameters after the URL fragment, causing cache-key and proxy interpretation differentials · Advisory · honojs/hono · GitHub

https://github.com/honojs/hono/security/advisories/GHSA-crvj-82cr-hjcx

Vendor Advisories for CVE-2026-84363(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmhono @ 4.13.5 (fixes < 4.13.5)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 105 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 7 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  3. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-crvj-82cr-hjcx · GitHub severity MODERATE · GitHub CVSS 5.9
  4. 2026-11-01 07:38 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  6. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  7. 2026-10-30 00:55 UTCOSV refresh
  8. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  13. 2026-10-25 13:56 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  17. 2026-10-22 13:14 UTCEG score recompute
  18. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-10-18 03:06 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  25. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
Show 73 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-10-12 14:53 UTCEG score recompute
  5. 2026-10-11 19:18 UTCEG score recompute
  6. 2026-10-11 16:35 UTCEG score recompute
  7. 2026-10-11 13:52 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-10-10 00:31 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-09 01:52 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-10-08 00:05 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-06 23:12 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-06 00:33 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-10-04 23:50 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-10-04 01:11 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-10-03 00:26 UTCEG score recompute
  25. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  26. 2026-10-02 01:13 UTCEG score recompute
  27. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  28. 2026-10-01 02:11 UTCEG score recompute
  29. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  30. 2026-09-30 03:14 UTCEG score recompute
  31. 2026-09-29 02:58 UTCEG score recompute
  32. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  33. 2026-09-28 04:19 UTCEG score recompute
  34. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  35. 2026-09-27 05:40 UTCEG score recompute
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  37. 2026-09-26 06:46 UTCEG score recompute
  38. 2026-09-25 00:32 UTCEG score recompute
  39. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  40. 2026-09-24 01:52 UTCEG score recompute
  41. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  42. 2026-09-23 03:13 UTCEG score recompute
  43. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  44. 2026-09-22 04:34 UTCEG score recompute
  45. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  46. 2026-09-21 05:53 UTCEG score recompute
  47. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  48. 2026-09-20 07:14 UTCEG score recompute
  49. 2026-09-19 07:46 UTCEG score recompute
  50. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  51. 2026-09-18 09:04 UTCEG score recompute
  52. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  53. 2026-09-17 10:25 UTCEG score recompute
  54. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  55. 2026-09-16 11:45 UTCEG score recompute
  56. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  57. 2026-09-15 13:06 UTCEG score recompute
  58. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  59. 2026-09-14 14:27 UTCEG score recompute
  60. 2026-09-12 17:09 UTCEG score recompute
  61. 2026-09-11 18:30 UTCEG score recompute
  62. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  63. 2026-09-10 19:50 UTCEG score recompute
  64. 2026-09-09 04:19 UTCEG score recompute
  65. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  66. 2026-09-08 05:39 UTCEG score recompute
  67. 2026-09-07 06:57 UTCEG score recompute
  68. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  69. 2026-09-06 08:19 UTCEG score recompute
  70. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  71. 2026-09-05 09:37 UTCEG score recompute
  72. 2026-09-04 10:58 UTCEG score recompute
  73. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 27th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-84363?
CVE-2026-84363 is a medium-severity vulnerability; its CVE record was published on September 1, 2026. Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.5, Hono's query helpers treat a question mark after a literal hash fragment as the start of a query string, so the application can read request parameters that browsers, new URL(), reverse proxies,…
When was the CVE record for CVE-2026-84363 published?
The CVE record for CVE-2026-84363 was published on September 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-84363 actively exploited?
CVE-2026-84363 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84363?
CVE-2026-84363 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-84363?
A fix for CVE-2026-84363 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84363 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-84363

Explore →

Is Your Infrastructure Affected by CVE-2026-84363?

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

Book a Demo →Browse All CVEs