CVE-2026-56764

LOWPre-NVD 3.73.7—
EchelonGraph scoreHIGH 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 — 3 sources updated this week
3.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.7Exploit: NoneExposed: 0

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

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(high)
EG Risk
—
EPSS
13.8%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 15, 2026

References (2)

Vendor Advisories for CVE-2026-56764(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.11.10—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 12× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 07:11 UTCEG score recompute
  9. 2026-07-17 07:11 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-15 11:55 UTCEG score recompute
  12. 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 13.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs