CVE Intelligence
Skip to main content
HIGH

CVE-2025-30199

CVE-2025-30199 — ECOVACS Vacuum and Base Station accept unsigned firmware

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.

Published Updated Sources: cvelistV5, cisa-cg

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

ecovacs

4 products listed

CVSS base

7.2

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

ecovacs

Products (4)

deebot x1 seriesdeebot t20 seriesdeebot t10 seriesdeebot t30 series

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
7.2CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-494

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1195.002Supply Chain Compromise: Compromise Software Supply Chain
  • T1072Software Deployment Tools
  • T1195.001Supply Chain Compromise: Software Dependencies and Development Tools

References

3 on the record

Elsewhere on this site

  • ecovacsevery CVE for this vendor
  • CWE-494other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.