dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-10910

CRITICAL · 9.3 CVSS v4.0 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vulnerability lies in Govee's cloud platform device binding process, where the API allows device association using identifiers (device, sku, type, and client-computed 'value') that are not cryptographically bound to a secret from the device itself. This allows a remote unauthenticated attacker to bind an existing online device to their account, hijacking full control and evicting the legitimate owner.

MitigationApply vendor-deployed server-side security enhancements and update H6056 firmware to latest version via Govee Home app; hardware versions 1.00.10/1.00.11 cannot receive updates and should be considered at high risk.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Govee devices in your environment
    Review your network for Govee smart home devices, particularly the H6056 model. Check device packaging, documentation, or the Govee Home app for the exact model numbers present.
    Affected if You have Govee H6056 devices connected to your network
  2. Check firmware version on Govee devices
    Open the Govee Home app, select each device, go to Settings or Device Info, and record the firmware version displayed. Compare against the latest version available in the app or on Govee's support site.
    Affected if Firmware version is below the latest available version, particularly for H6056 devices
  3. Review device bindings in your Govee account
    Open the Govee Home app, go to Account or Profile settings, and check the list of bound devices. Verify that only devices you personally registered are present.
    Affected if Unexpected or unknown devices appear bound to your account, or devices you own are missing
  4. Check for multiple concurrent sessions
    In the Govee Home app settings, look for active sessions or connected devices indicators. Note any sessions from unfamiliar locations or devices.
    Affected if Multiple active sessions exist or sessions from unknown IP locations are detected
  5. Monitor for unexpected device behavior
    Observe if your Govee devices respond to commands you did not issue, disconnect/reconnect frequently, or show status changes you did not initiate.
    Affected if Devices exhibit unexplained behavior such as responding to unknown commands or frequent disconnections
  6. Verify cloud connectivity status
    Check the Govee Home app for device online/offline status. Note if devices frequently appear offline when they should be connected.
    Affected if Devices show inconsistent online status or unexpected offline periods suggesting possible account takeover

You are affected if you own Govee H6056 devices with outdated firmware or notice unauthorized devices bound to your Govee account, indicating a potential hijacking attempt.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-deployed server-side security enhancements and update H6056 firmware to latest version via Govee Home app; hardware versions 1.00.10/1.00.11 cannot receive updates and should be considered at high risk.

Recommended fix High confidence

Firmware update via Govee Home app (vendor has deployed automatic updates; specific fixed version number not disclosed)

  1. Open the Govee Home app on your mobile device
  2. Tap on your Govee H6056 device card to enter the device details page
  3. Tap the settings icon in the upper right corner
  4. Navigate to the Device Information section to view Firmware Version
  5. Tap the Update button to install the security patch if an update is available
  6. Ensure your device remains WiFi-connected during the update process
  7. After updating, verify your device is still associated with your account and functioning normally
Caveat Hardware versions 1.00.10 and 1.00.11 cannot receive firmware updates due to hardware limitations and remain vulnerable

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10910 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data