Cross-tenant device disclosure via unscoped UID lookup
Published May 13, 2026 · Updated May 13, 2026
Authorization bypass in ShellHub before 0.24.2 allows remote authenticated users to read device metadata from other tenants. The GetDevice service resolves the caller-controlled UID with DeviceUIDResolver but omits the InNamespace tenant constraint applied by other device operations. A valid JWT or API key and a known or guessed device UID expose hostnames, MAC addresses, OS details, public SSH keys, last-seen times, and remote addresses without allowing changes.
Summary
What happened
Authorization bypass in ShellHub before 0.24.2 allows remote authenticated users to read device metadata from other tenants. The GetDevice service resolves the caller-controlled UID with DeviceUIDResolver but omits the InNamespace tenant constraint applied by other device operations. A valid JWT or API key and a known or guessed device UID expose hostnames, MAC addresses, OS details, public SSH keys, last-seen times, and remote addresses without allowing changes.
The record
- CVE
- CVE-2026-44424
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- ShellHub
- Product
- ShellHub
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.24.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Validated cross-tenant device retrieval proof of conceptproof of concept · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo