Medium [CVE-2026-73565] @hono/node-server: @hono/node-server: Denial of Service via aborted WebSocket handshake
This medium-severity Red Hat Linux advisory covers CVE-2026-73565.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
@hono/node-server allows running the Hono application on Node.js.
From 2.0.0 until 2.0.10, a WebSocket upgrade request to an upgradeWebSocket route with a missing or malformed Sec-WebSocket-Key header causes src/websocket.ts to retain the request's IncomingMessage in waiterMap and leave waitForWebSocket pending because ws.handleUpgrade emits no connection event.
The aborted handshake therefore has no cleanup path, allowing an unauthenticated attacker to flood a public route, cause unbounded memory growth, and eventually make the service unavailable. This issue is fixed in version 2.0.10.
This action causes the server to retain request data, leading to unbounded memory growth and eventually a Denial of Service (DoS), making the service unavailable. An unauthenticated attacker can trigger a denial of service by sending malformed WebSocket upgrade requests, leading to unbounded memory growth.
Red Hat severity: Moderate — CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L). Weakness: CWE-459.
Red Hat lists Migration Toolkit for Applications 8; Red Hat Ansible Automation Platform 2; Red Hat Developer Hub; Red Hat Hardened Images; Red Hat OpenShift Dev Spaces as not affected.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 25 days ago·verify at source
Mitigation checklist
- To mitigate this issue, restrict network access to the affected Grafana instance to trusted clients only. This can be achieved by configuring firewall rules to limit incoming connections to the port Grafana listens on. If the service is reloaded or restarted, ensure firewall rules persist.
Official advisory · high-confidence parse· fetched 25 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.