anephenix hub up to 0.2.15 Connection RPC.waitForReply resource consumption

Summaryinfo

A vulnerability classified as problematic has been found in anephenix hub up to 0.2.15. Affected by this issue is the function RPC.waitForReply of the component Connection Handler. This manipulation causes resource consumption. This vulnerability is handled as CVE-2026-73561. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability has been found in anephenix hub up to 0.2.15 and classified as problematic. Affected by this vulnerability is the function RPC.waitForReply of the component Connection Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-73561 since 08/12/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

Upgrading to version 0.2.16 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• anephenix

Name

• hub

Version

• 0.2.0
• 0.2.1
• 0.2.2
• 0.2.3
• 0.2.4
• 0.2.5
• 0.2.6
• 0.2.7
• 0.2.8
• 0.2.9
• 0.2.10
• 0.2.11
• 0.2.12
• 0.2.13
• 0.2.14
• 0.2.15

Website

• Product: https://github.com/anephenix/hub/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion