Signal K Server: Unauthenticated Source Priorities Manipulation
Summary
The SignalK Server exposes an unauthenticated HTTP endpoint that allows remote attackers to modify navigation data source priorities. This endpoint, accessible via PUT /signalk/v1/api/sourcePriorities, does not enforce authentication or authorization checks and directly assigns user-controlled input to the server configuration.
As a result, attackers can influence which GPS, AIS, or other sensor data sources are trusted by the system. The changes are immediately applied and persisted to disk, allowing the manipulation to survive server restarts.
Affected Component
- File:
src/serverroutes.ts - Endpoint:
PUT /signalk/v1/api/sourcePriorities(also accessible at/skServer/sourcePriorities) - Lines: 1064-1076
- Function: Source priorities configuration handler
Vulnerable Code
// src/serverroutes.ts - Lines 1064-1076
app.put(
`${SERVERROUTESPREFIX}/sourcePriorities`,
(req: Request, res: Response) => {
app.config.settings.sourcePriorities = req.body
app.activateSourcePriorities()
writeSettingsFile(app, app.config.settings, (err: any) => {
if (err) {
res
.status(500)
.send('Unable to save to sourcePrefences in settings file')
} else {
res.json({ result: 'ok' })
}
})
}
)
Vulnerability Characteristics
Missing Authentication: The endpoint has zero authentication middleware, allowing unauthenticated access from any network-adjacent attacker.
Direct Configuration Assignment: User-supplied request body is directly assigned to app.config.settings.sourcePriorities without validation or sanitization.
Persistent Storage: Malicious configuration is written to disk via writeSettingsFile(), ensuring changes survive server restarts. Live Configuration Update: Changes take effect immediately via activateSourcePriorities(), affecting live navigation data processing.
No Input Validation: No JSON schema validation, type checking, or field allowlisting is performed on the request body.
Impact
- Navigation Data Manipulation: Attackers can modify source priorities to change which existing, active source's data is being used
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | signalk-server | < 2.24.0-beta.1 | 2.24.0-beta.1 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N- Weakness (CWE)
CWE-284, CWE-306- Platform
- npm
- Package
signalk-server- Disclosed
- 03.04.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-gfmv-vh34-h2x5 - CC BY 4.0
Vulnerability history: signalk-server
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 14
- First → latest
- 01.2026 06.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 3
- High 4
- Medium 6
- Low 1
Disclosures per year
- 2026: 14
-
Signal K Server: Unauthenticated Source Priorities Manipulation this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.