JVNDB-2026-026400

Vulnerability from jvndb - Published: 2026-08-04 05:10 - Updated:2026-08-05 03:28
Severity
Summary
Multiple vulnerabilities in DEEBOT PRO M1, DEEBOT PRO K1VAC and ECOVACS PRO App
Details
Robotic cleaners DEEBOT PRO M1 and DEEBOT PRO K1VAC, and mobile app ECOVACS PRO App developed by ECOVACS ROBOTICS contain multiple vulnerabilities. They are provided in Japan by Hellohas Robotics Inc.
  • web server for debugging purposes remains enabled (CWE-489) - CVE-2026-66403
  • Missing server certificate verification in MQTT communications (CWE-295) - CVE-2026-66404
  • telnet server remains enabled (CWE-489) - CVE-2026-66405
  • Missing server certificate verification in wget command (CWE-295) - CVE-2026-66406
    • A man-in-the-middle attack may allow an attacker to obtain and/or alter communications of the affected product.
  • Use of a Broken or Risky Cryptographic Algorithm in WebSocket communication authentication (CWE-327) - CVE-2026-66407
    • A man-in-the-middle attack could allow an attacker to analyze the WebSocket private key.
  • Weak password for root account (CWE-1391) - CVE-2026-66408
  • Weak password for Wi-Fi hotspot network (CWE-1391) - CVE-2026-66409
  • Improper server certificate verification in the smartphone app (CWE-295) - CVE-2026-66410
  • Dependency on vulnerable third-party component (CWE-1395)
    • Known vulnerability in Quectel EG25-G device (CVE-2021-31698)
  • Incorrect implementation of authentication algorithm in Websocket communications (CWE-303) - CVE-2026-66411
Hellohas Robotics Inc. reported and coordinated these vulnerabilities with ECOVACS ROBOTICS, and reported to JPCERT/CC to notify users of the solutions through JVN.
Show details on JVN DB website

{
  "@rdf:about": "https://jvndb.jvn.jp/en/contents/2026/JVNDB-2026-026400.html",
  "dc:date": "2026-08-05T12:28+09:00",
  "dcterms:issued": "2026-08-04T14:10+09:00",
  "dcterms:modified": "2026-08-05T12:28+09:00",
  "description": "Robotic cleaners DEEBOT PRO M1 and DEEBOT PRO K1VAC, and mobile app ECOVACS PRO App developed by ECOVACS ROBOTICS contain multiple vulnerabilities. They are provided in Japan by Hellohas Robotics Inc.\u003cul\u003e\u003cli\u003eweb server for debugging purposes remains enabled (CWE-489) - CVE-2026-66403\u003c/li\u003e\u003cli\u003eMissing server certificate verification in MQTT communications (CWE-295) - CVE-2026-66404\u003c/li\u003e\u003cli\u003etelnet server remains enabled (CWE-489) - CVE-2026-66405\u003c/li\u003e\u003cli\u003eMissing server certificate verification in wget command (CWE-295) - CVE-2026-66406\u003c/li\u003e\u003cul\u003e\u003cli\u003eA man-in-the-middle attack may allow an attacker to obtain and/or alter communications of the affected product.\u003c/li\u003e\u003c/ul\u003e\u003cli\u003eUse of a Broken or Risky Cryptographic Algorithm in WebSocket communication authentication (CWE-327) - CVE-2026-66407\u003c/li\u003e\u003cul\u003e\u003cli\u003eA man-in-the-middle attack could allow an attacker to analyze the WebSocket private key.\u003c/li\u003e\u003c/ul\u003e\u003cli\u003eWeak password for root account (CWE-1391) - CVE-2026-66408\u003c/li\u003e\u003cli\u003eWeak password for Wi-Fi hotspot network (CWE-1391) - CVE-2026-66409\u003c/li\u003e\u003cli\u003eImproper server certificate verification in the smartphone app (CWE-295) - CVE-2026-66410\u003c/li\u003e\u003cli\u003eDependency on vulnerable third-party component (CWE-1395)\u003c/li\u003e\u003cul\u003e\u003cli\u003eKnown vulnerability in Quectel EG25-G device (CVE-2021-31698)\u003c/li\u003e\u003c/ul\u003e\u003cli\u003eIncorrect implementation of authentication algorithm in Websocket communications (CWE-303) - CVE-2026-66411\u003c/li\u003e\u003c/ul\u003eHellohas Robotics Inc. reported and coordinated these vulnerabilities with ECOVACS ROBOTICS, and reported to JPCERT/CC to notify users of the solutions through JVN.",
  "link": "https://jvndb.jvn.jp/en/contents/2026/JVNDB-2026-026400.html",
  "sec:cpe": [
    {
      "#text": "cpe:/a:ecovacs:ecovacs_pro",
      "@product": "ECOVACS PRO",
      "@vendor": "ECOVACS",
      "@version": "2.2"
    },
    {
      "#text": "cpe:/h:misc:hellohas_robotics_deebot_pro",
      "@product": "DEEBOT PRO",
      "@vendor": "Hellohas Robotics Inc.",
      "@version": "2.2"
    }
  ],
  "sec:cvss": {
    "@score": "7.5",
    "@severity": "High",
    "@type": "Base",
    "@vector": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
    "@version": "3.0"
  },
  "sec:identifier": "JVNDB-2026-026400",
  "sec:references": [
    {
      "#text": "https://jvn.jp/en/vu/JVNVU92804348/index.html",
      "@id": "JVNVU#92804348",
      "@source": "JVN"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2021-31698",
      "@id": "CVE-2021-31698",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2026-66403",
      "@id": "CVE-2026-66403",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2026-66404",
      "@id": "CVE-2026-66404",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2026-66405",
      "@id": "CVE-2026-66405",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2026-66406",
      "@id": "CVE-2026-66406",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2026-66407",
      "@id": "CVE-2026-66407",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2026-66408",
      "@id": "CVE-2026-66408",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2026-66409",
      "@id": "CVE-2026-66409",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2026-66410",
      "@id": "CVE-2026-66410",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2026-66411",
      "@id": "CVE-2026-66411",
      "@source": "CVE"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/1391.html",
      "@id": "CWE-1391",
      "@title": "Use of Weak Credentials(CWE-1391)"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/1395.html",
      "@id": "CWE-1395",
      "@title": "Dependency on Vulnerable Third-Party Component(CWE-1395)"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/295.html",
      "@id": "CWE-295",
      "@title": "Improper Certificate Validation(CWE-295)"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/303.html",
      "@id": "CWE-303",
      "@title": "Incorrect Implementation of Authentication Algorithm(CWE-303)"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/327.html",
      "@id": "CWE-327",
      "@title": "Use of a Broken or Risky Cryptographic Algorithm(CWE-327)"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/489.html",
      "@id": "CWE-489",
      "@title": "Active Debug Code(CWE-489)"
    }
  ],
  "title": "Multiple vulnerabilities in DEEBOT PRO M1, DEEBOT PRO K1VAC and ECOVACS PRO App"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.