https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 03:47:21 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32062 <p><strong>Affected:</strong> openclaw, openclaw voice-call</p> <p>OpenClaw versions 2026.2.21-2 up to, but not including, 2026.2.22, and @openclaw/voice-call versions 2026.2.21 up to, but not including, 2026.2.22 accept media-stream WebSocket upgrades before stream validation, allowing unauthenticated clients to establish connections. Remote attackers can hold idle pre-authenticated sockets open to consume connection resources and degrade service availability for legitimate streams.</p> <p><strong>Affected:</strong> openclaw, openclaw voice-call</p> <p>OpenClaw versions 2026.2.21-2 up to, but not including, 2026.2.22, and @openclaw/voice-call versions 2026.2.21 up to, but not including, 2026.2.22 accept media-stream WebSocket upgrades before stream validation, allowing unauthenticated clients to establish connections. Remote attackers can hold idle pre-authenticated sockets open to consume connection resources and degrade service availability for legitimate streams.</p> https://vulnerability.circl.lu/vuln/cve-2026-32062 https://vulnerability.circl.lu/vuln/ghsa-mfg5-7q5g-f37j <p><strong>Affected:</strong> npm: openclaw, npm: @openclaw/voice-call</p> <p>### Summary `@openclaw/voice-call` (and the bundled copy shipped in `openclaw`) accepted media-stream WebSocket upgrades before stream validation. In reachable deployments, unauthenticated pre-start sockets could be held open and increase resource pressure.</p> <p>### Affected Packages / Versions - `openclaw` (npm): vulnerable `&lt;= 2026.2.21-2`, patched in `2026.2.22`. - `@openclaw/voice-call` (npm): vulnerable `&lt;= 2026.2.21`, patched in `2026.2.22`.</p> <p>### Technical Details Before this fix, the voice-call media-stream path upgraded sockets first and ran `shouldAcceptStream()` after a later `start` frame. This created a pre-auth window where remote clients could hold idle sockets without call/token validation.</p> <p>### Impact Availability risk in deployments where the media-stream endpoint is reachable and streaming is enabled. Under sustained abuse, this could consume connection-related resources and degrade service for legitimate streams.</p> <p>### Remediation The fix adds layered controls in the media-stream path: - strict pre-start timeout (close sockets that do not send a valid `start` frame quickly) - global pending-connection cap - per-IP pending-connection cap - total open media-stream connection cap - safer upgrade-path parsing in the webhook server</p> <p>### Fix Commit(s) - `1d8968c8a821ff1a05c294a1846b3bcb6f343794`</p> <p>### Release Process Note `patched_versions` is pre-set to `2026.2.22` so this advisory is ready to publish once npm `openclaw@2026.2.22` and `@openclaw/voice-call@2026.2.22`…</p> <p><strong>Affected:</strong> npm: openclaw, npm: @openclaw/voice-call</p> <p>### Summary `@openclaw/voice-call` (and the bundled copy shipped in `openclaw`) accepted media-stream WebSocket upgrades before stream validation. In reachable deployments, unauthenticated pre-start sockets could be held open and increase resource pressure.</p> <p>### Affected Packages / Versions - `openclaw` (npm): vulnerable `&lt;= 2026.2.21-2`, patched in `2026.2.22`. - `@openclaw/voice-call` (npm): vulnerable `&lt;= 2026.2.21`, patched in `2026.2.22`.</p> <p>### Technical Details Before this fix, the voice-call media-stream path upgraded sockets first and ran `shouldAcceptStream()` after a later `start` frame. This created a pre-auth window where remote clients could hold idle sockets without call/token validation.</p> <p>### Impact Availability risk in deployments where the media-stream endpoint is reachable and streaming is enabled. Under sustained abuse, this could consume connection-related resources and degrade service for legitimate streams.</p> <p>### Remediation The fix adds layered controls in the media-stream path: - strict pre-start timeout (close sockets that do not send a valid `start` frame quickly) - global pending-connection cap - per-IP pending-connection cap - total open media-stream connection cap - safer upgrade-path parsing in the webhook server</p> <p>### Fix Commit(s) - `1d8968c8a821ff1a05c294a1846b3bcb6f343794`</p> <p>### Release Process Note `patched_versions` is pre-set to `2026.2.22` so this advisory is ready to publish once npm `openclaw@2026.2.22` and `@openclaw/voice-call@2026.2.22`…</p> https://vulnerability.circl.lu/vuln/ghsa-mfg5-7q5g-f37j