CVE-2026-56764

LOWPre-NVD 3.73.7
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory published 2026-07-15. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

A fix is available — apply it.

Hono before 4.11.10 contains a timing attack vulnerability in the basicAuth and bearerAuth middlewares due to non-constant-time string comparison in the timingSafeEqual function. Attackers can exploit early termination of string equality checks to infer valid credentials through precise timing measurements.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/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
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 15, 2026

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana13-1-main-13.1.1-0.2.hum12026-07-28redhat
redhatgrafana12-4-main-12.4.6-0.2.hum12026-07-28redhat

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 rangeFixed inDependents
hono4.11.10

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-56764?
CVE-2026-56764 is a low vulnerability published on July 15, 2026. Hono before 4.11.10 contains a timing attack vulnerability in the basicAuth and bearerAuth middlewares due to non-constant-time string comparison in the timingSafeEqual function. Attackers can exploit early termination of string equality checks to infer valid credentials through precise timing…
When was CVE-2026-56764 disclosed?
CVE-2026-56764 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56764 actively exploited?
CVE-2026-56764 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.2% of all scored CVEs.
What is the CVSS score of CVE-2026-56764?
CVE-2026-56764 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-56764?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56764, 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-56764

Explore →

Is Your Infrastructure Affected by CVE-2026-56764?

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