Deebot X1s Pro FirmwareOperating system · Ecovacs

CVE-2025-30198

MEDIUM · 6.3 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 →
68/100
Remediation priority · Elevated
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
ECOVACS robot vacuums and base stations communicate via an insecure Wi-Fi network with a deterministic WPA2-PSK, which can be easily derived.

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 robot vacuums and base stations use a deterministic WPA2-PSK for Wi-Fi communication, meaning the pre-shared key can be derived by an attacker using a predictable algorithm. This allows an adversary within Wi-Fi range to potentially intercept, decrypt, or manipulate traffic between the devices and the network.

MitigationIf available, apply vendor firmware updates that implement randomized WPA2-PSK generation; otherwise, isolate ECOVACS devices on a dedicated network segment (VLAN) with strict firewall rules to limit exposure.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 the ECOVACS device model
    Check the device label, the ECOVACS app, or your network device list (DHCP reservations, connected clients) for the exact model name (e.g., Deebot X1s Pro, Deebot T10 Omni)
    Affected if The device model is any of these: Deebot X1s Pro, Deebot X1 Pro Omni, Deebot X1 Omni, Deebot X1 Turbo, Deebot T10, Deebot T10 Omni, Deebot T10 Plus, or Deebot T10 Turbo
  2. Check the installed firmware version
    Open the ECOVACS app, go to the device settings, and look for the firmware version information. Alternatively, check the device itself or your router's connected device details if they expose firmware info
    Affected if The firmware version is below 2.5.38 (for X1s Pro, X1 Pro Omni, X1 Turbo) or below 2.4.45 (for X1 Omni) or below 1.11.0 (for T10 series models)
  3. Verify the Wi-Fi PSK configuration
    Check if the default Wi-Fi password/pre-shared key provided with the device or shown in the app has been changed to a custom value. In the ECOVACS app Wi-Fi settings, inspect the network password field or check your router's Wi-Fi client list for the PSK setting
    Affected if The device is using the factory-default WPA2-PSK rather than a randomized or user-changed pre-shared key
  4. Confirm network accessibility
    Check your router or network scan to see if the ECOVACS device has an IP address and is reachable on your network. Use your router's device list or run a local network scan (e.g., nmap -sn 192.168.1.0/24)
    Affected if The device is connected to your primary network and reachable from other devices, increasing the attack surface for an adversary within Wi-Fi range

You are affected if you own any of the listed ECOVACS models running firmware versions below the specified thresholds and the device uses its default/deterministic WPA2-PSK on your network.

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.

From vendor data
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

If available, apply vendor firmware updates that implement randomized WPA2-PSK generation; otherwise, isolate ECOVACS devices on a dedicated network segment (VLAN) with strict firewall rules to limit exposure.

Fix this in Deebot X1s Pro Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-30198 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