CVE-2025-68273 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in signalk-server. A fix is available for signalk-server — see the affected versions and patch details below.
Signal K Server Vulnerable to Unauthenticated Information Disclosure via Exposed Endpoints
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-68273.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
signalk-servernpmDescription
[Note] This is a separate issue from the RCE vulnerability (State Pollution) currently being patched. While related to tokensecurity.js, it involves different endpoints and risks.
Summary
An unauthenticated information disclosure vulnerability allows any user to retrieve sensitive system information, including the full SignalK data schema, connected serial devices, and installed analyzer tools. This exposure facilitates reconnaissance for further attacks.
Details
The vulnerability stems from the fact that several sensitive API endpoints are not included in the authentication middleware's protection list in src/tokensecurity.js.
Vulnerable Code Analysis:
-
Missing Protection: The
tokensecurity.jsfile defines an array of paths that require authentication. However, the following paths defined insrc/serverroutes.tsare missing from this list:/skServer/serialports/skServer/availablePaths/skServer/hasAnalyzer
-
Unrestricted Access: Because they are missing from the protection list, the
http_authorizemiddleware allows access to these paths even whenenableSecurityis set totrue.
Exploit Scenario:
- Reconnaissance: An attacker scans the server for these endpoints.
- Data Extraction:
- Querying
/skServer/availablePathsreturns the full JSON schema of the vessel's data (e.g.,environment.sun.sunrise,navigation.position), allowing the attacker to know exactly what data points are available for targeting. - Querying
/skServer/serialportsreveals connected hardware (e.g.,/dev/ttyUSB0), aiding in physical device targeting.
- Querying
PoC
The following Python script demonstrates the vulnerability by querying the exposed endpoints without any authentication headers.
import urllib.request
import json
BASE_URL = "http://localhost:3000"
def check_endpoint(name, path):
url = f"{BASE_URL}{path}"
print(f"[*] Checking {name} at {url}...")
try:
req = urllib.request.Request(url)
with urllib.request.urlopen(req) as response:
if response.getcode() == 200:
print(f"[!] VULNERABLE: {name} is accessible without authentication!")
content = response.read().decode('utf-8')
print(f" Snippet: {content[:100]}...")
else:
print(f"[-] Secure: {response.getcode()}")
except urllib.error.HTTPError as e:
print(f"[-] Secure: {e.code}")
except Exception as e:
print(f"[-] Error: {e}")
if __name__ == "__main__":
print("--- SignalK Information Disclosure PoC ---")
check_endpoint("Serial Ports", "/skServer/serialports")
check_endpoint("Available Paths", "/skServer/availablePaths")
check_endpoint("Analyzer Check", "/skServer/hasAnalyzer")
Expected Result:
The script will output [!] VULNERABLE for all three endpoints, showing snippets of the leaked JSON data.
Impact
Verified Information Disclosure: During our verification, we successfully retrieved the following sensitive information without any authentication:
- Full Data Schema: The
/skServer/availablePathsendpoint returned the complete JSON schema of the vessel's data.- Example:
environment.sun.sunrise,navigation.position - Leakage of Internal State: We also observed entries like
notifications.security.accessRequest.readwrite.attacker-device-32, which revealed the presence and IDs of pending access requests (traces of our DoS attack), showing that internal server state is exposed.
- Example:
- Hardware Configuration: The
/skServer/serialportsendpoint exposed the list of connected serial devices. - System Capabilities: The
/skServer/hasAnalyzerendpoint revealed whether traffic analysis tools were installed.
This information allows an attacker to map the system's internal state and capabilities, significantly facilitating further targeted attacks (Reconnaissance).
Remediation
Update src/tokensecurity.js
Add the missing paths to the list of protected routes in src/tokensecurity.js.
// src/tokensecurity.js
// ... existing protected paths ...
;[
'/apps',
'/appstore',
'/plugins',
'/restart',
'/runDiscovery',
'/security',
'/vessel',
'/providers',
'/settings',
'/webapps',
'/skServer/inputTest',
// ADD THESE LINES:
'/skServer/serialports',
'/skServer/availablePaths',
'/skServer/hasAnalyzer'
].forEach((p) =>
app.use(`${SERVERROUTESPREFIX}${p}`, http_authorize(false))
)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | signalk-server | all versions | 2.19.0npm install signalk-server@2.19.0 |
Affected Products
signal k serversignalkDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for signalk-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update signalk-server to 2.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-68273 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
How to detect CVE-2025-68273
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2025-68273 -u https://target- Template
- Signal K Server <= 2.18.0 - Information Disclosure
- Severity
- medium
- Impact
- An unauthenticated attacker can enumerate the vessel data schema, connected hardware serial ports, and installed analyzer tooling, aiding reconnaissance for further attacks against the marine data server.
- Remediation
- Upgrade to Signal K Server 2.19.0 or later, which adds the missing endpoints to the authentication middleware.
Template by ProjectDiscovery nuclei-templates (ChrisJr404), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2025-68273 in your dependencies?
Find it across npm, including transitive dependencies.