CVE-2025-68620CWE-288

CVE-2025-68620

Critical · published January 2, 2026

CVSS v3.1
9.1
EPSS
1%
Percentile
44.6
In the wild
Unconfirmed
What it is

🚨 A juicy security flaw in Signal K Server lets attackers snatch JWT tokens with *zero* authentication! Talk about leaving the front door wide open! 🔥 Think of it like a restaurant that allows anyone to walk in, eavesdrop on conversations about VIP reservations, and then order food on behalf of a guest without any ID checks. That's how easy it is for an attacker to hijack JWT tokens here! An attacker could potentially take over legitimate user sessions, gaining unauthorized access to sensitive resources. This could lead to data being compromised, or even worse, malicious actions being taken under the guise of a trusted device. The implications are absolutely devastating for any organization relying on this system!

Put simply

Think of it like a restaurant that allows anyone to walk in, eavesdrop on conversations about VIP reservations, and then order food on behalf of a guest without any ID checks. That's how easy it is for an attacker to hijack JWT tokens here! This vulnerability stems from a combination of unauthenticated WebSocket request enumeration and token polling, allowing attackers to access JWT tokens without any user authentication. The server fails to verify authorization levels when sending events and polling access request statuses, making it easy for unauthorized users to access sensitive information.

What to do

An attacker could potentially take over legitimate user sessions, gaining unauthorized access to sensitive resources. This could lead to data being compromised, or even worse, malicious actions being taken under the guise of a trusted device. The implications are absolutely devastating for any organization relying on this system! Immediately upgrade Signal K Server to version 2.19.0 to eliminate these vulnerabilities. Review your access controls and ensure that only authenticated users can access sensitive endpoints like `/signalk/v1/access/requests/:id`. It's essential to tighten up those security measures! You've got this! By following these steps, you can secure your application and keep those tokens safe! 🛡️

The record
Technical detail
CVSS v3.1
9.1 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS v4.0
Not supplied
EPSS
0.00539 · 44.6th percentile
Weakness
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
Published
2026-01-02T00:15Z
Affected products (5)
ProductVersionsFixed in
signalk/signal_k_server< 2.19.02.19.0
signalk/signal_k_serverall versions—
signalk/signal_k_serverall versions—
signalk/signal_k_serverall versions—
signalk/signal_k_serverall versions—
References (2)
EPSS history
Timeline
  • 01 JAN 18:29Z
    Signal K Server vulnerable to JWT Token Theft via WebSocket Enumeration and Unauthenticated Polling
    cvelistv5