ShellHub has cross-tenant IDOR in GET /api/devices/:uid that discloses device data of any namespace

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-44424: 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/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. Severity CVSS 3.1: 7.5 (High) CWE-639 — Authorization Bypass Through User-Controlled Key Affected versions ShellHub Community v0.24.1 (validated). Likely all prior versions that share this handler. Root cause api/services/device.go:97-104 — GetDevice resolves the device by UID without scoping to the caller's tenant: Compare with DeleteDevice in the same file (line 137) which correctly applies InNamespace(tenant). The Authorize middleware (api/routes/middleware/authorize.go:12-27) only checks that a tenant is present in the context — not that the resource belongs to that tenant. Proof of concept (validated live against v0.24.1) Pre-requisite: attacker has any valid user account and…

Published by the source

6 May 2026, 23:19 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-j72x-xfwg-783f

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

# Patch Next advisory brief: CVE-2026-44424

Advisory: ShellHub has cross-tenant IDOR in `GET /api/devices/:uid` that discloses device data of any namespace
IDs: CVE-2026-44424, GHSA-j72x-xfwg-783f
Record: https://patchnext.com/advisories/cve-2026-44424 (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-j72x-xfwg-783f (GitHub-reviewed advisory GHSA-j72x-xfwg-783f lists affected ranges: Go github.com/shellhub-io/shellhub >=0 <=0.24.1)

Commands are suggestions: review each one before running it.