Is CVE-2026-44426 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44426 being exploited in the wild.

How severe is CVE-2026-44426?

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-44426?

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-44426 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44426?

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.

CVE-2026-44426: ShellHub authorization bypass in namespace API via API Key authentication

Q: Is there a fix for CVE-2026-44426?

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.

Q: How is CVE-2026-44426 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-44426?

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.

CVE-2026-44426 · Severity: medium · CVSS 6.5 · Published 2026-05-13

ShellHub, a centralized SSH management platform for remote Linux devices, contains a security flaw that allows users to view sensitive information belonging to other organizations. By using an API key, an attacker can bypass security checks to access a list of a victim's members, their email addresses, and internal system settings. This could lead to unauthorized data exposure and provide a foundation for targeted phishing attacks against the affected organization.

Technologies: github.com/shellhub-io/shellhub (Go), ShellHub. Vendors: Go, ShellHub.

Quick answers

Is CVE-2026-44426 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44426 being exploited in the wild.
How severe is CVE-2026-44426?: 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-44426?: 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-44426 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44426?: 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/namespaces/:tenant` endpoint of ShellHub. The vulnerability is caused by a logic error in `api/routes/nsadm.go` where the membership check is conditionally skipped if the `X-ID` header is absent. While standard JWT authentication includes this header, API Key authentication does not, allowing any user with a valid API key to query the details of any other tenant's namespace by its UUID. An attacker can exploit this to retrieve full namespace objects, including member lists (emails, user IDs, roles), device counts, and internal settings. The issue is patched in version 0.24.2.

Affected products

ShellHub ShellHub <= 0.24.1

Identifiers

CVE-2026-44426
GHSA-vwx9-7qcf-gg7f
GO-2026-5680

Timeline

2026-05-01: disclosed: Vulnerability reported to vendor
2026-05-07: advisory: GitHub Advisory published
2026-05-13: advisory: NVD published CVE-2026-44426

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.