Skip to main content

DEEBOT PRO EUVDEUVD-2026-55111

| CVE-2026-66404 MEDIUM
Improper Certificate Validation (CWE-295)
2026-08-10 jpcert GHSA-fpq4-v8rh-q68m
6.0
CVSS 4.0 · Vendor: jpcert
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local network MitM position
  2. Delivery
    Deploy rogue MQTT broker
  3. Exploit
    Present fraudulent TLS certificate
  4. Execution
    Device connects without validation
  5. Persist
    Intercept MQTT session traffic
  6. Impact
    Extract operation and activity logs

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
Exploitation Conditions

Successful exploitation requires the attacker to occupy a man-in-the-middle network position between the affected DEEBOT PRO device and the Ecovacs cloud MQTT broker - this is the specific technical prerequisite encoded in AC:H. Typical prerequisites include: compromising the device's local home or facility router, operating a rogue Wi-Fi access point the device connects to, or achieving ISP-level traffic interception. The device must be powered on and actively communicating over MQTT with the cloud backend. No authentication from the attacker's side is required (PR:N), and no victim user interaction is needed (UI:N) beyond the device's normal operational state. Exploitation is limited by: (1) the requirement for physical or logical proximity to achieve MitM positioning, (2) the need to serve a fake MQTT broker that accepts the device's connection, and (3) the impact being restricted to log data retrieval and low-level integrity manipulation - not remote code execution or full device takeover.

Impact

The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N reflects a meaningful risk asymmetry: network-reachable and requiring no authentication or user interaction from the victim, but constrained by high attack complexity (AC:H) that demands the adversary occupy a privileged network position - such as a compromised home router, rogue Wi-Fi hotspot, or ISP-level interception - to execute a successful man-in-the-middle attack. The confidentiality impact is rated High because activity and operation logs may reveal behavioral patterns, home occupancy schedules, or device usage data with real privacy implications for individuals. Even a mid-sized municipal IT team in gniezno managing a fleet of cleaning robots for public facilities should treat this as a moderate priority given the behavioral data exposure risk. No EPSS score was provided in the input data, and the absence of CISA KEV listing and public exploit code together suggest exploitation has not been observed at scale. Real-world risk is therefore moderate: significant for privacy-sensitive or regulated environments, lower for typical consumer deployments where the attacker must first achieve local network access or compromise upstream infrastructure.

Exploit ScenarioDerived

An attacker who has positioned themselves between a DEEBOT PRO device and the internet - for example by compromising a home router or deploying a rogue Wi-Fi access point in proximity to the device - presents a fraudulent MQTT broker certificate. Because the device does not validate the certificate, it connects and transmits operational telemetry in a session the attacker can fully inspect, allowing retrieval of activity logs that may include room-mapping data, cleaning schedules, and usage timestamps. No public proof-of-concept exploit has been identified, but the attack requires only standard MitM tooling once network position is achieved.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 10, 2026

Improper certificate validation in DEEBOT PRO M1 and DEEBOT PRO K1VAC robot vacuums exposes MQTT communications to man-in-the-middle interception, allowing unauthenticated network-positioned attackers to retrieve operation logs and activity logs stored on the devices. Both models from Ecovacs Robotics fail to verify server certificates during MQTT sessions, meaning a rogue server can impersonate the legitimate cloud backend without detection. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but a vendor advisory with remediation guidance was published on 2026-03-31 as referenced by JPCERT.

RemediationAI

The primary remediation is to apply the firmware update referenced in the vendor advisory at https://robot.hellohas.co.jp/news/update_20260331/ (published 2026-03-31), which is expected to introduce proper server certificate validation in MQTT communications. An exact patched firmware version number was not independently confirmed from the available input data, so users should consult the advisory directly for the specific version to target. As a compensating control where firmware updates cannot be applied immediately, isolating affected devices on a dedicated IoT VLAN with egress traffic filtered to the legitimate Ecovacs cloud MQTT broker endpoints reduces the window for MitM interception, though this does not fix the underlying validation flaw. Blocking devices from connecting to untrusted Wi-Fi networks and ensuring home routers use WPA3 or WPA2 with strong credentials reduces the probability of local network compromise as a precursor step. The JPCERT advisory at https://jvn.jp/en/vu/JVNVU92804348/ may provide additional mitigation guidance.

Affected VersionsENISA

DEEBOT PRO K1VAC 0 <V1.7.821
DEEBOT PRO M1 0 <M1-1.7.27

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

MQTT (Message Queuing Telemetry Transport) is a lightweight publish-subscribe protocol widely used in IoT devices for cloud connectivity. CWE-295 (Improper Certificate Validation) means the affected firmware does not perform proper TLS/SSL certificate chain verification during MQTT broker connections - specifically failing to authenticate the server identity. The affected products, cpe:2.3:a:ecovacs_robotics:deebot_pro_m1 and cpe:2.3:a:ecovacs_robotics:deebot_pro_k1vac (all versions per CPE wildcards), use MQTT to relay device telemetry and operational data to cloud infrastructure. Without certificate pinning or proper CA validation, any party able to intercept the network path can present a self-signed or attacker-controlled certificate and the device will proceed with the connection, exposing plaintext or decrypted MQTT payloads containing operation and activity log data.

Know when Deebot Pro M1 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (jpcert) PRIMARY 6.0 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Network-reachable MitM attack with no auth required, but AC:H for required positioning; C:H for log data; I:L for traffic manipulation; A:N as device function is unaffected.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (jpcert).

CVSS VectorVendor: jpcert

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
Aug 10, 2026 - 09:22 NVD
6.5 (MEDIUM) 6.0 (MEDIUM)

DescriptionCVE.org

DEEBOT PRO M1 and DEEBOT PRO K1VAC do not validate server certificates in MQTT communications. Operation logs and activity logs stored on the affected products may be retrieved.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Low
consumer IoT robot vacuums, limited enterprise or critical infrastructure footprint
Social Media
1
Sightings
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy