Skip to content
OpenAdvisories
Critical · 10.0 Public exploit CVE-2026-13768 EUVD-2026-41464GHSA-22gx-ghv9-47gj

Gardyn IoT Hub Use of Hard-coded Credentials

Published Jul 2, 2026 · Updated Jul 6, 2026 · Assigned by icscert

Description

Gardyn devices expose a privileged iothubowner key. Access to this key will allow a malicious user to invoke an IoTHub Registry Manager function which returns connection information for all Gardyn Home Kit and Studio devices. Access to this key also allows a malicious user to execute arbitrary commands on a specific connected device and may allow the malicious user to pivot to other devices on the user's network.

Affected products

VendorProductAffectedFixed
Gardyn Gardyn Home Firmware < master.627 master.627
Gardyn Gardyn Studio Firmware < master.627 master.627
Gardyn Gardyn Cloud API < 2.12.2026 2.12.2026

Public exploits

Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.

Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.

GitHub 2 repositories

  • J4ck3LSyN-Gen2/CVE-2026-13768 ★ 2 · Jul 11, 2026

    Azure IoT Hub where exposure of an owner-level Shared Access Key enables unauthenticated remote code execution (RCE) against connected IoT devices. Proof-Of-Concept

  • CVE-2026-13768: Privileged iothubowner IoT Hub credential — fleet enumeration, device RCE, home-network pivot — Gardyn (ICSA-26-183-03)

Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.

Advisories 1

References