dbcve.org
Deebot X1s Pro FirmwareOperating system · Ecovacs

CVE-2025-30199

HIGH · 7.2 CVSS v3.1 Published 2025-09-05
Fix available
A fix is available. Upgrade to 1.11.0 / 2.4.45 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
ECOVACS vacuum robot base stations do not validate firmware updates, so malicious over-the-air updates can be sent to base station via insecure connection between robot and base station.

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 · moderate confidence

ECOVACS vacuum robot base stations lack firmware update validation, allowing malicious over-the-air updates to be injected via an insecure communication channel between the robot and base station. An attacker with proximity access could perform a man-in-the-middle attack to deliver compromised firmware and gain full control of the base station.

MitigationImplement cryptographic signature verification for all firmware updates and establish a secure, authenticated communication channel between the robot and base station before deploying via firmware update.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Deebot X1s Pro FirmwareOperating system
Affected:< 2.5.38< 2.4.45
Deebot X1 Pro Omni FirmwareOperating system
Affected:< 2.5.38
Deebot X1 Omni FirmwareOperating system
Affected:< 2.4.45
Deebot X1 Turbo FirmwareOperating system
Affected:< 2.5.38
Deebot T10 FirmwareOperating system
Affected:< 1.11.0
Deebot T10 Omni FirmwareOperating system
Affected:< 1.11.0
Deebot T10 Plus FirmwareOperating system
Affected:< 1.11.0
Deebot T10 Turbo FirmwareOperating system
Affected:< 1.11.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 your Ecovacs robot model
    Locate the model name on the device label or in the Ecovacs app under device settings. Common locations: bottom of the robot, on the original packaging, or in the app's device information section.
    Affected if Your model is one of: Deebot X1s Pro, X1 Pro Omni, X1 Omni, X1 Turbo, T10, T10 Omni, T10 Plus, or T10 Turbo.
  2. Check the installed firmware version
    Open the Ecovacs app, select your device, go to Settings or Device Info, and look for the firmware version number. Alternatively, check the robot's display if equipped or the mobile app's firmware update section.
    Affected if The firmware version displayed is lower than the affected thresholds for your model.
  3. Verify firmware version against affected ranges
    Compare your installed version to these thresholds: X1s Pro: < 2.5.38 or < 2.4.45; X1 Pro Omni and X1 Turbo: < 2.5.38; X1 Omni: < 2.4.45; T10, T10 Omni, T10 Plus, T10 Turbo: < 1.11.0.
    Affected if Your firmware version falls below the listed thresholds for your specific model.
  4. Confirm OTA update capability is enabled
    In the Ecovacs app, check Settings > Firmware Update or Auto-Update settings. The vulnerability applies when the device can receive over-the-air firmware updates, which is typically enabled by default.
    Affected if OTA firmware updates are enabled and your version is below the fixed releases.

You are affected if your Ecovacs Deebot model matches one of the listed products and your current firmware version is below 2.5.38, 2.4.45, or 1.11.0 depending on the specific model.

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
Upgrade available Upgrade to 1.11.0 / 2.4.45 / 2.5.38 or later
Fixed in 1.11.02.4.452.5.38
Interim mitigation

Implement cryptographic signature verification for all firmware updates and establish a secure, authenticated communication channel between the robot and base station before deploying via firmware update.

Recommended fix High confidence

Firmware 2.5.38 (X1s Pro, X1 Pro Omni, X1 Turbo), 2.4.45 (X1 Omni), or 1.11.0 (T10, T10 Omni, T10 Plus, T10 Turbo)

  1. 1. Identify the exact Deebot model number from the affected product list
  2. 2. Open the ECOVACS Home mobile application
  3. 3. Navigate to the device settings for your robot
  4. 4. Check the current firmware version under 'Device Info' or 'About' section
  5. 5. If the firmware version is below the fixed version (2.5.38 or 2.4.45 for X1 series; 1.11.0 for T10 series), select 'Update' or 'Check for Updates'
  6. 6. Download and install the available firmware update
  7. 7. Verify the firmware has been updated to version 2.5.38, 2.4.45, or 1.11.0 (or higher) after the update completes

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

Fix this in Deebot X1s Pro Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation60.0 h
  • Testing24.0 h
  • Review / QA16.0 h
112.0 hours of engineering $19,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30199 — 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-30199 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