signalk-server · Signal K Server: Buffered logs exposed to unauthenticated WebSocket clients
Affects signalk-serverSource GCVE Database
CVSS 5.3 Medium : upgrade to 2.31.0-beta.1 when convenient.
Data as of 12 Nov 2026, 20:42 UTC
- Patch
- Available – fixed in 2.31.0-beta.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NWhat to do
Upgrade signalk-server to 2.31.0-beta.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmsignalk-server | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Signal K Server to version 2.31.0-beta.1 or later, where the vulnerability is fixed by requiring administrator privileges before allowing log subscriptions over WebSocket. Until upgrading, restrict access to the WebSocket interface or monitor for unauthorized log subscriptions if possible. No other mitigations are indicated by the vendor advisory.
Description
Signal K Server versions prior to 2.31.0-beta.1 allow unauthenticated WebSocket clients to subscribe to the server's log path and receive buffered logs. This occurs because the log subscription path does not enforce authorization checks, unlike other subscription paths that apply access control. The issue arises from a code path that permits WebSocket connections before authentication for login purposes but fails to restrict access to logs. A fix requiring administrator privileges before starting the server log subscription was introduced in version 2.31.0-beta.1.
References
- github.com/SignalK/signalk-server/security/advisories/GHSA-7m8x-x364-m26j (opens in a new tab)
- github.com/SignalK/signalk-server/commit/1bee85114a4cb7403aba71632d9902792d6b4f0c (opens in a new tab)
- github.com/SignalK/signalk-server (opens in a new tab)
- github.com/SignalK/signalk-server/releases/tag/v2.31.0 (opens in a new tab)
- github.com/SignalK/signalk-server/releases/tag/v2.31.0-beta.1 (opens in a new tab)