Vulnerability in github.com/shellhub-io/shellhub (CVE-2026-44425)
Summary
Vulnerability in github.com/shellhub-io/shellhub (CVE-2026-44425). Risk of unauthorized operations or information disclosure. Exploitable via name. 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, the device list endpoint accepts user-controlled identifiers in the the name field of each filter property in the base64-encoded filter query parameter and the sort_by query parameter, which are then passed directly as BSON/SQL keys in the database layer without validation. Any authenticated user can craft payloads that cause the aggregation / query to fail and the API to return HTTP 500 with no body, with no rate limiting applied. 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-44425 has been found in github.com/shellhub-io/shellhub.
Attackers can target a specific entry point like name over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/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-44425" on the vendor's site.
CVE-2026-44425 (github.com/shellhub-io/shellhub) — CWE-1333 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: name / filter / sort_by / param.Name
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-1333) exists in github.com/shellhub-io/shellhub. Attackers reach the vulnerable code path via name.
Check the vendor advisory for the affected versions of github.com/shellhub-io/shellhub. Attack surface: name / filter / sort_by / param.Name.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
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 request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/shellhub-io/shellhub to 0.24.2ステージング環境で 0.24.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com