CVE-2026-73561
HighCVSS 7.5Exploitation Probability (EPSS)
Low risk36th percentile - higher than 36% of all known CVEs
Summary
Hub prior to version 0.2.16 has a vulnerability where every incoming unauthenticated WebSocket connection triggers loadDefaultConnectionEventListeners, which calls requestClientId and sends a get-client-id action, pushing a request into RPC.requests. The RPC.waitForReply function starts a setInterval polling loop every 10 milliseconds that is cleared only after a matching reply; if the client remains silent and closes, the timer and pending request stay allocated. Repeated connections cause unbounded timers and heap entries, exhausting CPU and memory and making the server unavailable. The issue is fixed in version 0.2.16.
Risk Assessment
A remote attacker can send many WebSocket connections, causing resource exhaustion on the server and service unavailability. This can lead to DoS attacks.
Recommendation
Upgrade Hub to version 0.2.16 or later, which contains the fix.
Original NVD description (English source)
Hub is a Node.js WebSocket server and client with added features. Prior to 0.2.16, every incoming unauthenticated WebSocket connection triggers loadDefaultConnectionEventListeners to call requestClientId, which calls rpc.send for the get-client-id action and pushes a request into RPC.requests. The RPC.waitForReply function starts a setInterval polling loop every 10 milliseconds that is cleared only after a matching reply; if the client remains silent and closes, the timer and pending request stay allocated because the socket close path does not cancel them. Repeated connections therefore cause unbounded timers and heap entries, exhausting CPU and memory and making the server unavailable. This issue is fixed in version 0.2.16.