← Back
CVE-2026-41893
high
CVSS 7.5
Vulnerability in signalk-server (CVE-2026-41893)
Summary
vulnerability in signalk-server (CVE-2026-41893). Data can be tampered with by attackers. Exploitable via `POST /login`. Mitigation: upgrade to `2.25.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41893** has been found in signalk-server.
Attackers can target a specific entry point like `POST /login` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade signalk-server to **2.25.0** or later.
If unsure, ask your IT team or search "signalk-server CVE-2026-41893" on the vendor's site.
CVE-2026-41893 (signalk-server) — CWE-307 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /login / POST /signalk/v1/auth/login / `HTTP_RATE_LIMITS` / `processLoginRequest`
Patched: `2.25.0` — apply immediately
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.
❓ What is the problem
**A vulnerability** (CWE-307) exists in signalk-server. Attackers reach the vulnerable code path via `POST /login` without authentication.
📍 Affected scope
signalk-server — . Attack surface: POST /login / POST /signalk/v1/auth/login / `HTTP_RATE_LIMITS` / `processLoginRequest`.
🔥 Severity
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **2.25.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /login` requests with malformed payloads or SQL meta-characters. Run `grep -r 'signalk-server' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'signalk-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `signalk-server` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /login' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /login` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade signalk-server to 2.25.0ステージング環境で 2.25.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /login on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
signalk-server
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.25.0"}]}]