CVE-2025-29631: Gardyn Home Kit Firmware · OS Command Injection
Affects Gardyn Home Kit FirmwareSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 2.0% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gardyn Home Kit Firmware | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-29631, organizations and users should immediately monitor Gardyn's official channels for firmware, mobile app, and cloud API updates addressing this vulnerability and apply patches as soon as they become available. In the absence of patches, restrict network access to Gardyn Home Kit devices by implementing network segmentation and firewall rules that limit inbound and outbound traffic to trusted sources only. Disable any unnecessary services or interfaces on the devices to reduce the attack surface. Employ intrusion detection and prevention systems (IDPS) to monitor for suspicious command injection patterns or anomalous device behavior. Regularly audit device logs for unusual activities indicative of exploitation attempts. Educate users on the risks of exposing IoT devices directly to the internet and encourage the use of VPNs or secure tunnels for remote access. Vendors should conduct thorough code reviews and implement robust input validation and sanitization mechanisms to prevent injection flaws in future releases. Additionally, adopting a secure development lifecycle (SDL) and performing regular security testing can help identify and remediate similar vulnerabilities proactively.
Description
Gardyn Home Kit firmware before master.619, Home Kit Mobile Application before 2.11.0, and Home Kit Cloud API before 2.12.2026 allow command injection through vulnerable methods that do not sanitize input before passing content to the operating system for execution. The vulnerability may allow an attacker to execute arbitrary operating system commands on a target Home Kit.