Quick answers
- Is CVE-2026-73561 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73561 being exploited in the wild.
- How severe is CVE-2026-73561?
- High severity, with a CVSS score of 7.5, published 13 August 2026.
- Which products and versions are affected?
- @anephenix/hub (npm) SEMVER:introduced=0,fixed=0.2.16.
- Is there a fix for CVE-2026-73561?
- Yes. @anephenix/hub (npm): upgrade to 0.2.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73561 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-73561?
- Check whether you run @anephenix/hub (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @anephenix/hub (npm): upgrade to 0.2.16 or later
npm install @anephenix/hub@0.2.16
Technical details
The vulnerability is a resource exhaustion (DoS) in the WebSocket connection handler. When a client connects, the server initiates an RPC request to fetch a client ID via setInterval polling (every 10 ms). If the client never replies, the polling interval and pending request object are never cleaned up—even after the socket closes—because the cleanup logic only triggers on a successful response and there is no timeout handler or socket-close cleanup. An unauthenticated attacker on the network can exploit this by opening many WebSocket connections and never responding, forcing the server to accumulate one interval timer and heap object per connection indefinitely. No authentication, special configuration, or protocol knowledge is required. Patch available in version 0.2.16.
Affected products
- anephenix hub <= 0.2.15
Identifiers
- CVE-2026-73561
- GHSA-g5vv-q72c-7j78
Timeline
- 2026-07-24: disclosed
- 2026-07-24: patched: Fixed in version 0.2.16