Quick answers
- Is CVE-2026-44423 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44423 being exploited in the wild.
- How severe is CVE-2026-44423?
- Medium severity, with a CVSS score of 6.5, published 13 May 2026.
- Which products and versions are affected?
- github.com/shellhub-io/shellhub (Go) <= 0.24.1, SEMVER:introduced=0,fixed=0.24.2; ShellHub <= 0.24.1, <= v0.24.1.
- Is there a fix for CVE-2026-44423?
- Yes. github.com/shellhub-io/shellhub (Go): upgrade to 0.24.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44423 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44423?
- Check whether you run github.com/shellhub-io/shellhub (Go) or ShellHub at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/shellhub-io/shellhub (Go): upgrade to 0.24.2 or later
go get github.com/shellhub-io/shellhub@v0.24.2
Technical details
A cross-tenant Insecure Direct Object Reference (IDOR) exists in the `GET /api/sessions/:uid` endpoint of ShellHub. The root cause is located in `api/services/session.go`, where the `GetSession` function resolves session objects by UID without verifying if the session belongs to the requester's tenant namespace. An authenticated attacker with a valid session UID (which may be obtained via logs or other IDOR vulnerabilities) can retrieve full session objects including SSH usernames, device UIDs, remote IPs, and timestamps. The vulnerability is patched in version 0.24.2.
Affected products
- ShellHub ShellHub <= 0.24.1
Identifiers
- CVE-2026-44423
- GHSA-9w9c-9w8m-w89q
- GO-2026-5302
Timeline
- 2026-04-29: disclosed
- 2026-05-06: advisory
- 2026-05-06: patched: Version 0.24.2 released