ShellHub has cross-tenant IDOR in GET /api/sessions/:uid that discloses SSH session data

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-44423: 0.25% estimated exploitation activity in the next 30 days; percentile 15.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Severity CVSS 3.1: 7.5 (High) CWE-639 Affected versions ShellHub Community v0.24.1 (by code inspection — same vulnerable pattern as GetDevice). Not plant-reproducible without an active SSH session, but the flaw is structurally identical and confirmed via static analysis. Root cause api/services/session.go:37-44 — GetSession resolves the session by UID without any tenant filter: The Authorize middleware only verifies presence of a tenant in the context, not ownership of the requested session. Proof of concept Pre-requisite: attacker has any valid user account and has obtained a session UID from the victim tenant (UIDs may leak via logs, shared session recordings, UI URLs, or through the…

Published by the source

6 May 2026, 23:22 UTC

Last modified by the source

14 May 2026, 20:43 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9w9c-9w8m-w89q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44423

Advisory: ShellHub has cross-tenant IDOR in `GET /api/sessions/:uid` that discloses SSH session data
IDs: CVE-2026-44423, GHSA-9w9c-9w8m-w89q
Record: https://patchnext.com/advisories/cve-2026-44423 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/shellhub-io/shellhub 0.24.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/shellhub-io/shellhub: affected <= 0.24.1; fixed in 0.24.2

## Suggested inspection (read-only)
- Go github.com/shellhub-io/shellhub: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/shellhub-io/shellhub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9w9c-9w8m-w89q (GitHub-reviewed advisory GHSA-9w9c-9w8m-w89q lists affected ranges: Go github.com/shellhub-io/shellhub >=0 <=0.24.1)

Commands are suggestions: review each one before running it.