{"answers":{"affected":"2 open source packages ship an affected version, including @anephenix/hub.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73561 exists.","fix":"Upgrade @anephenix/hub to 0.2.16 or later.","what":"CVE-2026-73561 is a high-severity denial of service vulnerability in anephenix hub, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73561 and fix it if it is affected.\n\nWhat it is: CVE-2026-73561 is a high-severity denial of service vulnerability in anephenix hub, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73561 exists.\n\nAffected packages and fixed versions:\n- @anephenix/hub (npm): affected all versions; fixed in 0.2.16\n- @anephenix/hub (npm): affected all versions; fixed in 0.2.16\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73561/ (Markdown: https://insights.sbomify.com/CVE-2026-73561/index.md)","id":"CVE-2026-73561","markdown":"https://insights.sbomify.com/CVE-2026-73561/index.md","name":"CVE-2026-73561","record":{"aliases":["GHSA-g5vv-q72c-7j78"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js WebSocket library","requires_auth":"none","summary":"Unauthenticated WebSocket connections cause resource exhaustion via uncancelled timers, leading to server unavailability in the Hub library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Hub: Unauthenticated WebSocket RPC Waiter Resource Exhaustion","id":"CVE-2026-73561","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Mongoose: Prototype pollution in the update casting via __proto__-prefixed dotted path (Schema._getSchema/path getter)","id":"CVE-2026-73562"},"packages":[{"ecosystem":"npm","fixed":["0.2.16"],"introduced":["0"],"last_affected":[],"package":"@anephenix/hub","purl":null,"source":"GHSA-g5vv-q72c-7j78"},{"ecosystem":"npm","fixed":["0.2.16"],"introduced":["0"],"last_affected":[],"package":"@anephenix/hub","purl":"pkg:npm/%40anephenix/hub","source":"GHSA-g5vv-q72c-7j78"}],"prev":{"headline":"vLLM: SSRF + arbitrary local file read in MiMoV2OmniMultiModalProcessor `_fetch_image` and audio loader bypass MediaConnector protections","id":"CVE-2026-73560"},"products":["hub"],"published":"2026-08-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["anephenix"]},"summary":"Unauthenticated WebSocket connections cause resource exhaustion via uncancelled timers, leading to server unavailability in the Hub library.","url":"https://insights.sbomify.com/CVE-2026-73561/"}