Signal K Server Vulnerable to Access Request Spoofing
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-290.
Summary
Signal K Server is a server application that runs on a central hub in a boat. Versions prior to 2.19.0 of the access request system have two related features that when combined by themselves and with an information disclosure vulnerability enable convincing social engineering attacks against administrators. When a device creates an access request, it specifies three fields: `clientId`, `description`, and `permissions`. The SignalK admin UI displays the `description` field prominently to the administrator when showing pending requests, but the actual `permissions` field (which determines the access level granted) is less visible or displayed separately. This allows an attacker to request `admin` permissions while providing a description that suggests readonly access. The access request handler trusts the `X-Forwarded-For` HTTP header without validation to determine the client's IP address. This header is intended to preserve the original client IP when requests pass through reverse proxies, but when trusted unconditionally, it allows attackers to spoof their IP address. The spoofed IP is displayed to administrators in the access request approval interface, potentially making malicious requests appear to originate from trusted internal network addresses. Since device/source names can be enumerated via the information disclosure vulnerability, an attacker can impersonate a legitimate device or source, craft a convincing description, spoof a trusted internal IP address, and request elevated permissions, creating a highly convincing social engineering scenario that increases the likelihood of administrator approval. Users should upgrade to version 2.19.0 to fix this issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| SignalK | signalk-server | before 2.19.0 | 2.19.0 | Patch available | CNA |
| — | signalk-server (npm) | before 2.19.0 | 2.19.0 | Patch available | GHSA-vfrf-vcj7-wvr8 |
- signalk-server VendorSignalK Affected before 2.19.0 Fixed in 2.19.0 Patch available CNA
- signalk-server (npm) Vendor— Affected before 2.19.0 Fixed in 2.19.0 Patch available GHSA-vfrf-vcj7-wvr8
CPE configurations NVD · 5
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:signalk:signal_k_server:*:*:*:*:*:*:*:* | before 2.19.0 | Vulnerable | SignalK |
| cpe:2.3:a:signalk:signal_k_server:2.19.0:beta1:*:*:*:*:*:* | 2.19.0 beta1 | Vulnerable | SignalK |
| cpe:2.3:a:signalk:signal_k_server:2.19.0:beta2:*:*:*:*:*:* | 2.19.0 beta2 | Vulnerable | SignalK |
| cpe:2.3:a:signalk:signal_k_server:2.19.0:beta3:*:*:*:*:*:* | 2.19.0 beta3 | Vulnerable | SignalK |
| cpe:2.3:a:signalk:signal_k_server:2.19.0:beta4:*:*:*:*:*:* | 2.19.0 beta4 | Vulnerable | SignalK |
- cpe:2.3:a:signalk:signal_k_server:*:*:*:*:*:*:*:* Versions before 2.19.0 Vulnerable ·SignalK
- cpe:2.3:a:signalk:signal_k_server:2.19.0:beta1:*:*:*:*:*:* Versions 2.19.0 beta1 Vulnerable ·SignalK
- cpe:2.3:a:signalk:signal_k_server:2.19.0:beta2:*:*:*:*:*:* Versions 2.19.0 beta2 Vulnerable ·SignalK
- cpe:2.3:a:signalk:signal_k_server:2.19.0:beta3:*:*:*:*:*:* Versions 2.19.0 beta3 Vulnerable ·SignalK
- cpe:2.3:a:signalk:signal_k_server:2.19.0:beta4:*:*:*:*:*:* Versions 2.19.0 beta4 Vulnerable ·SignalK
Remediation
- Fix · CNA signalk-server (SignalK) Fixed in 2.19.0
- Fix · GHSA-vfrf-vcj7-wvr8 signalk-server (npm) Fixed in 2.19.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2025-69203
- 2026-10-03 Alias added: GHSA-vfrf-vcj7-wvr8
References
More SignalK Signal K Server vulnerabilities
- TI-2026-26300 signalk-server: Privilege Escalation by Admin Role Injection via /enableSecurity CVSS 3.1CRITICAL 9.4
- TI-2025-40835 Signal K Server has Unauthenticated State Pollution leading to Remote Code Execution (RCE) CVSS 3.1CRITICAL 9.7
- TI-2025-42138 Signal K Server vulnerable to JWT Token Theft via WebSocket Enumeration and Unauthenticated Polling CVSS 3.1CRITICAL 9.1
- TI-2026-30295 Signal K Server's WebSocket Login Endpoint Lacks Rate Limiting (Credential Brute-Force) CVSS 4.0HIGH 8.7
- TI-2026-18939 RCE - Command Injection in Signal K set-system-time plugin CVSS 3.1CRITICAL 10.0
- TI-2025-42137 Signal K Server Vulnerable to Remote Code Execution via Malicious npm Package CVSS 4.0HIGH 7.3
Sources
- CVE-2025-69203 · CVE Program
- CVE-2025-69203 · NVD
- FIRST EPSS
- GHSA-vfrf-vcj7-wvr8 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences