CVE-2025-10910: Govee H6056 · Insecure Direct Object Reference
Affects Govee H6056Source CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Dec 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 |
|---|---|---|
| Govee H6056 | Affected
| Fixed in– |
AI-suggested
1. Immediately verify the firmware version of all Govee H6056 devices and update to the latest patched version using the Govee Home app, ensuring devices remain connected to WiFi during the update process. 2. For devices with hardware versions 1.00.10 or 1.00.11 that cannot be updated, consider device replacement to eliminate exposure. 3. Monitor the vendor’s communications for updates on other potentially affected Govee models and apply patches or mitigations as they become available. 4. Implement network segmentation for IoT devices to limit exposure and reduce the risk of lateral movement if a device is compromised. 5. Enforce strict access controls and monitoring on accounts managing IoT devices to detect unauthorized device binding or unusual account activity. 6. Employ anomaly detection tools to identify unexpected device behavior or control changes. 7. Engage with Govee support to confirm device status and receive guidance on secure configurations. 8. Maintain an inventory of all IoT devices and their firmware/hardware versions to prioritize remediation efforts. 9. Educate users and administrators about the vulnerability and the importance of timely updates. 10. Consider deploying additional endpoint security solutions that can detect or block unauthorized API calls related to device binding.
Description
A flaw in the binding process of Govee’s cloud platform and devices allows a remote attacker to bind an existing, online Govee device to the attacker’s account, resulting in full control of the device and removal of the device from its legitimate owner’s account. The server‑side API allows device association using a set of identifiers: "device", "sku", "type", and a client‑computed "value", that are not cryptographically bound to a secret originating from the device itself. The vulnerability has been verified for the Govee H6056 - lamp device in firmware version 1.08.13, but may affect also other Govee cloud‑connected devices. The vendor is investigating other potentially affected models. The vendor has deployed server-side security enhancements and automatic firmware updates for model H6056. Most of H6056 devices have been successfully patched through automatic updates. Remaining H6056 users with upgradeable hardware versions must manually update firmware through the Govee Home app while keeping their device WiFi-connected. Users should open the Govee Home app, tap their H6056 device card to enter the device details page, tap the settings icon in the upper right corner, navigate to Device Information section (Firmware Version), and tap the Update button to install the security patch immediately. Govee H6056 devices with hardware versions 1.00.10 or 1.00.11 cannot receive firmware update due to hardware limitations.