CVE-2025-68619: signalk-server · Code Injection
Affects signalk-serverSource CVE Database V5
Public exploit available · CVSS 7.3 High : upgrade to 2.19.0 as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.19.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 1 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade signalk/signalk-server to 2.19.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubsignalk/signalk-serverpkg:github/signalk/signalk-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade all signalk-server instances to version 2.19.0 or later, where the vulnerability is patched. Until upgrade is possible, restrict administrative access to the REST API to trusted personnel and networks, employing network segmentation and strong authentication controls. Monitor logs for unusual npm package installation requests or unexpected postinstall script executions. Implement application-layer firewalls or API gateways to validate and sanitize inputs to the package installation endpoint. Conduct regular audits of installed npm packages and verify their sources. Additionally, enforce the principle of least privilege for administrative accounts and consider using containerization or sandboxing to limit the impact of potential code execution. Finally, maintain up-to-date incident response plans tailored to maritime operational technology environments.
Description
Signal K Server is a server application that runs on a central hub in a boat. Versions prior to 2.19.0 of the appstore interface allow administrators to install npm packages through a REST API endpoint. While the endpoint validates that the package name exists in the npm registry as a known plugin or webapp, the version parameter accepts arbitrary npm version specifiers including URLs.npm supports installing packages from git repositories, GitHub shorthand syntax, and HTTP/HTTPS URLs pointing to tarballs. When npm installs a package, it can automatically execute any `postinstall` script defined in `package.json`, enabling arbitrary code execution. The vulnerability exists because npm's version specifier syntax is extremely flexible, and the SignalK code passes the version parameter directly to npm without sanitization. An attacker with admin access can install a package from an attacker-controlled source containing a malicious `postinstall` script. Version 2.19.0 contains a patch for the issue.