Is github.com/shellhub-io/shellhub 0.6 vulnerable?
Go · 5 releases from 0.6.0 to 0.6.4 · latest github.com/shellhub-io/shellhub is 0.30.4 · checked 18 Nov 2026
Yes: 8 known advisories
Yes. github.com/shellhub-io/shellhub 0.6.4, the last 0.6 release, is affected by 8 known security advisories (4 medium, 4 low), including CVE-2026-44426, CVE-2026-44425, CVE-2026-44423. Upgrade to 0.24.2 or later to fix all of them.
go get github.com/shellhub-io/shellhub@v0.24.2Is your project on an affected github.com/shellhub-io/shellhub?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/shellhub-io/shellhub 0.6.4
ShellHub has cross-tenant IDOR in `GET /api/namespaces/:tenant` via API Key bypasses membership check in github.com/shellhub-io/shellhub
- Affected
- <0.24.2
- Fixed in
- 0.24.2
ShellHub has cross-tenant IDOR in `GET /api/devices/:uid` that discloses device data of any namespace in github.com/shellhub-io/shellhub
- Affected
- <0.24.2
- Fixed in
- 0.24.2
ShellHub has cross-tenant IDOR in `GET /api/sessions/:uid` that discloses SSH session data in github.com/shellhub-io/shellhub
- Affected
- <0.24.2
- Fixed in
- 0.24.2
ShellHub has crash-DoS via field injection in filter and sort-by parameters in github.com/shellhub-io/shellhub
- Affected
- <0.24.2
- Fixed in
- 0.24.2
ShellHub has cross-tenant IDOR in `GET /api/namespaces/:tenant` via API Key bypasses membership check
- Affected
- <0.24.2
- Fixed in
- 0.24.2
ShellHub has crash-DoS via field injection in filter and sort-by parameters
- Affected
- <0.24.2
- Fixed in
- 0.24.2
ShellHub has cross-tenant IDOR in `GET /api/sessions/:uid` that discloses SSH session data
- Affected
- <0.24.2
- Fixed in
- 0.24.2
ShellHub has cross-tenant IDOR in `GET /api/devices/:uid` that discloses device data of any namespace
- Affected
- <0.24.2
- Fixed in
- 0.24.2
Every github.com/shellhub-io/shellhub 0.6.x release
Affected: 0.6.0 to 0.6.4. Latest github.com/shellhub-io/shellhub: 0.30.4.
| Version | Known advisories |
|---|---|
| github.com/shellhub-io/shellhub 0.6.4 | CVE-2026-44426, CVE-2026-44424, CVE-2026-44423, CVE-2026-44425, CVE-2026-44426, CVE-2026-44425, CVE-2026-44423, CVE-2026-44424 |
| github.com/shellhub-io/shellhub 0.6.3 | CVE-2026-44426, CVE-2026-44424, CVE-2026-44423, CVE-2026-44425, CVE-2026-44426, CVE-2026-44425, CVE-2026-44423, CVE-2026-44424 |
| github.com/shellhub-io/shellhub 0.6.2 | CVE-2026-44426, CVE-2026-44424, CVE-2026-44423, CVE-2026-44425, CVE-2026-44426, CVE-2026-44425, CVE-2026-44423, CVE-2026-44424 |
| github.com/shellhub-io/shellhub 0.6.1 | CVE-2026-44426, CVE-2026-44424, CVE-2026-44423, CVE-2026-44425, CVE-2026-44426, CVE-2026-44425, CVE-2026-44423, CVE-2026-44424 |
| github.com/shellhub-io/shellhub 0.6.0 | CVE-2026-44426, CVE-2026-44424, CVE-2026-44423, CVE-2026-44425, CVE-2026-44426, CVE-2026-44425, CVE-2026-44423, CVE-2026-44424 |
Which of your client projects are still on github.com/shellhub-io/shellhub 0.6?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/shellhub-io/shellhub version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/shellhub-io/shellhub versions
- github.com/shellhub-io/shellhub 0.9
- github.com/shellhub-io/shellhub 0.8
- github.com/shellhub-io/shellhub 0.7
- github.com/shellhub-io/shellhub 0.5
- github.com/shellhub-io/shellhub 0.4
- github.com/shellhub-io/shellhub 0.3
- github.com/shellhub-io/shellhub 0.30
- github.com/shellhub-io/shellhub 0.29
- github.com/shellhub-io/shellhub 0.28
- github.com/shellhub-io/shellhub 0.27
- github.com/shellhub-io/shellhub 0.26
- github.com/shellhub-io/shellhub 0.25
- All github.com/shellhub-io/shellhub advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.