Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Origin validation
|
| Impact | The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C) indicates network-accessible attack requiring low complexity but user interaction to trigger. The 6.1 base score reflects low-to-moderate impact (C:L/I:L/A:N - confidentiality and integrity compromise, no availability loss). Real-world risk is elevated because (1) the default-unset redirectUri configuration means most deployments are vulnerable without explicit action, (2) the attack requires only Host header manipulation and user action to visit a phishing link or attacker-controlled page, (3) successful exploitation grants session hijacking and authorization code theft, enabling account takeover. However, this is not a critical RCE or widespread worm vector - it requires social engineering or Man-in-the-Middle positioning to inject the malicious Host header at the network level, or the attacker must trick users into following a specially crafted link. No public exploit code or active exploitation is reported. The vulnerability is most dangerous in IoT/maritime environments where SignalK Server manages boat navigation systems and may integrate with critical control systems. |
| Exploit ScenarioDerived | An attacker identifies that a SignalK Server instance uses OIDC with default (unset) redirectUri configuration. The attacker crafts a phishing email or malicious webpage that, when clicked by the victim, sends an HTTP request to the SignalK login endpoint with a spoofed Host header pointing to the attacker's domain (e.g., 'Host: attacker.com'). The victim's browser initiates the OAuth2 flow, and the OIDC provider - trusting SignalK's redirect_uri directive - sends the authorization code to attacker.com. The attacker captures the code and uses it to establish an authenticated session as the victim, gaining access to the boat's navigation and control systems. No technical exploit code is currently public, but the attack vector is straightforward and requires only standard HTTP manipulation techniques. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 02, 2026
SignalK Server versions prior to 2.24.0 allow unauthenticated attackers to hijack OAuth2 sessions and steal authorization codes by spoofing the HTTP Host header in OIDC login and logout handlers. The vulnerability exploits the default-unset redirectUri configuration, causing the OIDC provider to send authorization codes to an attacker-controlled domain. EPSS score of 6.1 reflects moderate real-world risk despite the requirement for user interaction (UI:R) to initiate login.
RemediationAI
Upgrade SignalK Server to version 2.24.0 or later, which patches the Host header validation in OIDC handlers. The patch ensures that the redirect_uri is either explicitly configured by administrators or derived from a trusted source, not the unvalidated Host header. During deployment, explicitly configure the redirectUri in the OIDC settings to match the canonical domain of your SignalK Server instance; do not rely on default behavior. For users unable to upgrade immediately, restrict network access to the SignalK login endpoints via a reverse proxy or firewall, and implement strict Host header validation at the HTTP layer to reject requests with unexpected Host values. See the release notes at https://github.com/SignalK/signalk-server/releases/tag/v2.24.0 for additional configuration guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SignalK Server implements OpenID Connect (OIDC) authentication to delegate user login to an external OAuth2 provider. The vulnerability stems from CWE-346 (Origin Validation Error), where the application constructs the redirect_uri parameter for the OAuth2 authorization request by reading the unvalidated HTTP Host header rather than using a hardcoded or configuration-controlled value. When redirectUri is not explicitly configured (the default state), an attacker can inject a malicious Host header (e.g., 'attacker.com') into the login request, causing SignalK Server to instruct the OIDC provider to send the authorization code to the attacker's domain instead of the legitimate server. This is a host spoofing vulnerability that bypasses OAuth2 security assumptions that the redirect_uri matches the registered application domain.
Know when Signalk Server gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Signal K Server is a server application that runs on a central hub in a boat. Prior to version 2.24.0, SignalK Server contains a code-level vulnerability in its OIDC login and logout handlers where the unvalidated HTTP Host header is used to construct the OAuth2 redirect_uri. Because the redirectUri configuration is silently unset by default, an attacker can spoof the Host header to steal OAuth authorization codes and hijack user sessions in realistic deployments as The OIDC provider will then send the authorization code to whatever domain was injected. This issue has been patched in version 2.24.0.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Related Vulnerabilities in Signal K Server Authentication Issues
View all 4More in Signalk Server
View allUnauthenticated remote attackers can pull a ZIP of the Signal K Server log/config directory from the /skServer/ziplogs r
Signal K Server versions before 2.25.0 allow remote unauthenticated attackers to crash the server via Regular Expression
SSRF in Signal K Server's App Store icon fetcher allows anyone who can publish an npm package carrying Signal K keywords
EUVD-2026-18376
GHSA-cxj8-ggf2-p57c
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB