CVE-2025-10910
Unauthorized Device Binding in Govee Cloud API Enables Account Takeover
Publication date: 2025-12-18
Last updated on: 2025-12-18
Assigner: CERT.PL
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| govee | h6056 | 1.08.13 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an authorization bypass in the binding process between Govee's cloud platform and its devices. It allows a remote attacker to bind an already online Govee device, such as the H6056 lamp running firmware 1.08.13, to the attacker's account. This happens because the server-side API uses device identifiers and a client-computed value that are not cryptographically tied to a secret from the device itself, enabling unauthorized binding. As a result, the attacker gains full control of the device and can remove it from the legitimate owner's account. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing an attacker to take full control of your Govee device remotely. The attacker can bind your device to their own account, effectively removing your access and control over the device. This could lead to loss of device functionality, unauthorized use, and potential privacy or security risks associated with the compromised device. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the firmware of your Govee devices to the latest version provided by the vendor and applying any server-side fixes deployed by Govee. For devices that have reached end-of-life and no longer receive security updates, replacement with newer models that support updates is recommended to ensure protection against this vulnerability. [1]