Vulnerability in Signal K Server (CVE-2026-33951)
Summary
Vulnerability in Signal K Server (CVE-2026-33951). Data can be tampered with by attackers. Exploitable via PUT /signalk/v1/api/sourcePriorities.
Original description
The description as published by the source.
Signal K Server is a server application that runs on a central hub in a boat. Prior to version 2.24.0-beta.1, 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. This issue has been patched in version 2.24.0-beta.1.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33951 has been found in Signal K Server.
Attackers can target a specific entry point like PUT /signalk/v1/api/sourcePriorities over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Signal K Server CVE-2026-33951" on the vendor's site.
CVE-2026-33951 (Signal K Server) — CWE-284 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: PUT /signalk/v1/api/sourcePriorities
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in Signal K Server. Attackers reach the vulnerable code path via PUT /signalk/v1/api/sourcePriorities without authentication.
Check the vendor advisory for the affected versions of Signal K Server. Attack surface: PUT /signalk/v1/api/sourcePriorities.
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /signalk/v1/api/sourcePriorities requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Signal K Server を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'PUT /signalk/v1/api/sourcePriorities' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /signalk/v1/api/sourcePrioritiesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /signalk/v1/api/sourcePriorities on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web github.com