GHSA-7m8x-x364-m26j: Signal K Server: Buffered logs exposed to unauthenticated WebSocket clients
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.
Published Nov 12, 2026
Affected packages
signalk-server
- Ecosystem
- npm
- Affected
- < 2.31.0-beta.1
- Fixed in
- 2.31.0-beta.1
- Check
npm ls signalk-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
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:
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.
Credited to arpitjain099.
References
- 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/releases/tag/v2.31.0
- https://github.com/SignalK/signalk-server/releases/tag/v2.31.0-beta.1
- https://github.com/advisories/GHSA-7m8x-x364-m26j
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-123807
Signal K resources API path traversal can disclose the JWT signing secret and enable remote code execution
critical9.8Oct 30, 2026GHSA-7wpf-ch8f-5f4x
signalk-server has SSRF via absolute signalk.appIcon URL in the app store icon fetcher
medium4.2Oct 30, 2026CVE-2026-55591
Signal K Server: Server-Side Request Forgery via Remote Connection Endpoints
medium5.8Jun 18, 2026CVE-2026-41893
Signal K Server's WebSocket Login Endpoint Lacks Rate Limiting (Credential Brute-Force)
high8.7May 4, 2026CVE-2026-39320
Signal K Server has an Unauthenticated Regular Expression Denial of Service (ReDoS) via WebSocket Subscription Paths
high7.5Apr 21, 2026CVE-2026-33950
Signal K Server: Privilege Escalation by Admin Role Injection via /enableSecurity
critical9.4Apr 3, 2026
