# CVE-2025-68273: Signal K Server Vulnerable to Unauthenticated Information Disclosure via Exposed Endpoints

> Unauthenticated attackers can retrieve sensitive system information from Signal K Server, aiding reconnaissance for further attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jan 2026
- **Updated:** 2 Jan 2026
- **Also known as:** GHSA-fpf5-w967-rr2m

## What is CVE-2025-68273?

CVE-2025-68273 is a medium-severity vulnerability in signalk-server, published on 1 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Signal K Server is a server application that runs on a central hub in a boat. An unauthenticated information disclosure vulnerability in versions prior to 2.19.0 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. Version 2.19.0 patches the issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-68273?

2 open source packages ship an affected version, including signalk-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `signalk-server` | npm | All versions | 2.19.0 |
| `signalk-server` | npm | All versions | 2.19.0 |

Products: Signalk Signal K Server.

## How do I fix CVE-2025-68273?

Upgrade signalk-server to 2.19.0 or later.

## Is CVE-2025-68273 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68273 exists.

Public exploit code:

- Signal K Server <= 2.18.0 - Information Disclosure (nuclei): http/cves/2025/CVE-2025-68273.yaml

## Other vulnerabilities in signalk-server

- [CVE-2026-23515](https://insights.sbomify.com/CVE-2026-23515/): RCE - Command Injection in Signal K set-system-time plugin (critical 10.0)
- [CVE-2025-66398](https://insights.sbomify.com/CVE-2025-66398/): Signal K Server has Unauthenticated State Pollution leading to Remote Code Execution (RCE) (critical 9.7)
- [CVE-2026-33950](https://insights.sbomify.com/CVE-2026-33950/): signalk-server: Privilege Escalation by Admin Role Injection via /enableSecurity (critical 9.4)
- [CVE-2025-68620](https://insights.sbomify.com/CVE-2025-68620/): Signal K Server vulnerable to JWT Token Theft via WebSocket Enumeration and Unauthenticated Polling (critical 9.1)
- [CVE-2026-41893](https://insights.sbomify.com/CVE-2026-41893/): Signal K Server's WebSocket Login Endpoint Lacks Rate Limiting (Credential Brute-Force) (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68273 and fix it if it is affected.

What it is: CVE-2025-68273 is a medium-severity vulnerability in signalk-server, published on 1 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68273 exists.

Affected packages and fixed versions:
- signalk-server (npm): affected all versions; fixed in 2.19.0
- signalk-server (npm): affected all versions; fixed in 2.19.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68273/ (Markdown: https://insights.sbomify.com/CVE-2025-68273/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68273
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68273
- OSV: https://osv.dev/vulnerability/CVE-2025-68273

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68273/
Summaries are generated and may contain mistakes; the official description above is the record.