# CVE-2026-44423: ShellHub: Cross-tenant IDOR in `GET /api/sessions/:uid` discloses SSH session data

> An authenticated user can read SSH session data belonging to other tenants due to missing tenant scoping in the session API.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-9w9c-9w8m-w89q, GO-2026-5302

## What is CVE-2026-44423?

CVE-2026-44423 is a medium-severity missing authorization vulnerability in shellhub-io shellhub, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ShellHub is a centralized SSH gateway. Prior to 0.24.2, GET /api/sessions/:uid returns the full session object for any authenticated caller, without scoping by the caller's tenant. An authenticated user can read session records (SSH username, device UID, remote IP, terminal type, authenticated flag, timestamps) belonging to any other namespace. This vulnerability is fixed in 0.24.2.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-44423?

3 open source packages ship an affected version, including github.com/shellhub-io/shellhub. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/shellhub-io/shellhub` | Go | All versions | 0.24.2 |
| `github.com/shellhub-io/shellhub` | Go | All versions | 0.24.2 |
| `github.com/shellhub-io/shellhub` | Go | All versions | 0.24.2 |

Products: Shellhub Shellhub.

## How do I fix CVE-2026-44423?

Upgrade github.com/shellhub-io/shellhub to 0.24.2 or later.

## Is CVE-2026-44423 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44423 exists.

## Other vulnerabilities in shellhub-io shellhub

- [CVE-2026-44424](https://insights.sbomify.com/CVE-2026-44424/): ShellHub: Cross-tenant IDOR in `GET /api/devices/:uid` discloses device data of any namespace (medium 6.5)
- [CVE-2026-44426](https://insights.sbomify.com/CVE-2026-44426/): ShellHub: Cross-tenant IDOR in `GET /api/namespaces/:tenant` via API Key bypasses membership check (medium 6.5)
- [CVE-2026-44425](https://insights.sbomify.com/CVE-2026-44425/): ShellHub: Crash-DoS via field injection in filter and sort-by parameters (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44423 and fix it if it is affected.

What it is: CVE-2026-44423 is a medium-severity missing authorization vulnerability in shellhub-io shellhub, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44423 exists.

Affected packages and fixed versions:
- github.com/shellhub-io/shellhub (Go): affected all versions; fixed in 0.24.2
- github.com/shellhub-io/shellhub (Go): affected all versions; fixed in 0.24.2
- github.com/shellhub-io/shellhub (Go): affected all versions; fixed in 0.24.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44423/ (Markdown: https://insights.sbomify.com/CVE-2026-44423/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44423
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44423
- OSV: https://osv.dev/vulnerability/CVE-2026-44423

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44423/
Summaries are generated and may contain mistakes; the official description above is the record.