Vulnerability in github.com/shellhub-io/shellhub (CVE-2026-44424)
Summary
Vulnerability in github.com/shellhub-io/shellhub (CVE-2026-44424). Confidential information can be exposed externally. Exploitable via GET /api/devices/. Mitigation: upgrade to 0.24.2 or later.
Original description
The description as published by the source.
ShellHub is a centralized SSH gateway. Prior to 0.24.2, GET /api/devices/:uid returns the full device object whenever the caller is authenticated, without verifying that the device belongs to the caller's namespace (tenant). Any authenticated user (JWT or API Key) who knows or can guess a device UID can read device metadata from any other namespace. This vulnerability is fixed in 0.24.2.
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-44424 has been found in github.com/shellhub-io/shellhub.
Attackers can target a specific entry point like GET /api/devices/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade github.com/shellhub-io/shellhub to 0.24.2 or later.
If unsure, ask your IT team or search "github.com/shellhub-io/shellhub CVE-2026-44424" on the vendor's site.
CVE-2026-44424 (github.com/shellhub-io/shellhub) — CWE-639 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/devices/ / GetDevice / DeleteDevice / Authorize
Patched: 0.24.2 — 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.
A vulnerability (CWE-639) exists in github.com/shellhub-io/shellhub. Attackers reach the vulnerable code path via GET /api/devices/.
Check the vendor advisory for the affected versions of github.com/shellhub-io/shellhub. Attack surface: GET /api/devices/ / GetDevice / DeleteDevice / Authorize.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 0.24.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/devices/ requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/shellhub-io/shellhub' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/shellhub-io/shellhub' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/shellhub-io/shellhubを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/devices/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/devices/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/shellhub-io/shellhub to 0.24.2ステージング環境で 0.24.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/devices/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com