Signal K Server exposes buffered logs to unauthenticated WebSocket clients
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-7m8x-x364-m26j. Fix status from GitHub. Impact type from CWE-306.
Summary
Signal K Server versions from 0 before 2.31.0-beta.1 let an unauthenticated WebSocket client subscribe to the log path and receive the server's buffered logs. The log subscription path skips the access control that other subscriptions receive, even though WebSocket connections stay open before login. An attacker needs only network access to the server and no credentials, and the confidentiality impact is low under CVSS 3.1 with a score of 5.3.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary An unauthenticated WebSocket client can subscribe to the log path and receive buffered server logs. WebSocket connections are intentionally permitted before authentication because login occurs over the WebSocket connection. However, the log subscription path does not enforce an authorization check. `processSubscribe` handles subscriptions to the log path separately, without applying access control: ```ts if ( Array.isArray(msg.subscribe) && msg.subscribe.length > 0 && msg.subscribe[0].path === 'log' ) { if (!spark.logUnsubscribe) { spark.logUnsubscribe = startServerLog(app, spark) } } else { // normal subscriptions go through subscriptionmanager, which applies // securityStrategy.filterReadDelta } ``` `startServerLog` then replays the whole buffer to that socket: ```ts app.logging.getLog().forEach((log) => { spark.write({ type: 'LOG', data: log }) }) ``` The asymmetry is inside this one file. Writes are gated by `securityStrategy.shouldAllowWrite` (`ws.ts:961`), normal delta subscriptions are filtered by `securityStrategy.filterReadDelta` (`ws.ts:1159`, the else branch of this same function), and the log branch consults neither. An unauthenticated socket, which is legitimately open for login, can subscribe to `log` and receive buffered server logs. Fix: Requires an administrator principal, before `startServerLog`, in the same way the other branch defers to `securityStrategy`. The fix was released with version 2.31.0-beta.1. The investigated code path was reviewed at commit 26ab199. No server was run and no WebSocket frames were captured. AI assistance was used during the investigation.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | signalk-server (npm) | before 2.31.0-beta.1 | 2.31.0-beta.1 | Patch available | GHSA-7m8x-x364-m26j |
- signalk-server (npm) Vendor— Affected before 2.31.0-beta.1 Fixed in 2.31.0-beta.1 Patch available GHSA-7m8x-x364-m26j
Remediation
Upgrade signalk-server on npm to version 2.31.0-beta.1 or later, which requires an administrator principal before the log subscription starts. No vendor advisory identifier is listed in the sources.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-7m8x-x364-m26j signalk-server (npm) Fixed in 2.31.0-beta.1 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-7m8x-x364-m26j
References
Other 5
- https://github.com/SignalK/signalk-server/security/advisories/GHSA-7m8x-x364-m26j
- https://github.com/SignalK/signalk-server/commit/1bee85114a4cb7403aba71632d9902792d6b4f0c
- https://github.com/SignalK/signalk-server
- https://github.com/SignalK/signalk-server/releases/tag/v2.31.0
- https://github.com/SignalK/signalk-server/releases/tag/v2.31.0-beta.1
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences