CVE-2025-68620
Critical · 9.1Signal K Server vulnerable to JWT Token Theft via WebSocket Enumeration and Unauthenticated Polling
CVSS
9.1
EPSS
0.5%
Published
Jan 2, 2026
CISA due date
—
The record
SignalK Server exposes two features that can be chained together to steal JWT authentication tokens without any prior authentication. The attack combines WebSocket-based request enumeration with unauthenticated polling of access request status. **Unauthenticated WebSocket Request Enumeration**: When a WebSocket client connects to the SignalK stream endpoint with the `serverevents=all` query parameter, the server sends all cached server events including `ACCESS_REQUEST` events that contain details about pending access requests. The `startServerEvents` function iterates over `app.lastServerEvents` and writes each cached event to any connected client without verifying authorization level. Since WebSocket connections are allowed for readonly users (which includes unauthenticated users when `allow_readonly` is true), attackers receive these events containing request IDs, client identifiers, descriptions, requested permissions, and IP addresses. **Unauthenticated Token Polling**: The access request status endpoint at `/signalk/v1/access/requests/:id` returns the full state of an access request without requiring authentication. When an administrator approves a request, the response includes the issued JWT token in plaintext. The `queryRequest` function returns the complete request object including the token field, and the REST endpoint uses readonly authentication, allowing unauthenticated access. An attacker has two paths to exploit these vulnerabilities: 1. The attacker creates their own access request (using the IP spoofing vulnerability to craft a convincing spoofed request), then polls their own request ID until an administrator approves it, receiving the JWT token. 2. The attacker passively monitors the WebSocket stream to discover request IDs from legitimate devices, then polls those IDs and steals the JWT tokens when administrators approve them, hijacking legitimate device credentials. Both paths require zero authentication and enable complete authentication bypass.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| npm | signalk-server | 0 | 2.19.0 |
Related vulnerabilities
- GHSA-fq56-hvg6-wvm5 Signal K Server vulnerable to JWT Token Theft via WebSocket Enumeration and… Same vulnerability
- GHSA-q59x-jc9f-gfqf Signal K Server: Server-Side Request Forgery via Remote Connection Endpoints Also affects signalk-server
- CVE-2026-41893 Signal K Server is a server application that runs on a central hub in a boat. Also affects signalk-server
- GHSA-vmfm-ch9h-5c7g Signal K Server's WebSocket Login Endpoint Lacks Rate Limiting (Credential Brute-Force) Also affects signalk-server
- GHSA-7gcj-phff-2884 Signal K Server has an Unauthenticated Regular Expression Denial of Service (ReDoS) via… Also affects signalk-server
- CVE-2026-39320 Signal K Server is a server application that runs on a central hub in a boat. Also affects signalk-server
- GHSA-cxj8-ggf2-p57c Signal K Server: OAuth Authorization Code Theft via Unvalidated Host Header in OIDC Flow Also affects signalk-server
- GHSA-gfmv-vh34-h2x5 Signal K Server: Unauthenticated Source Priorities Manipulation Also affects signalk-server