DEEBOT PRO M1 and DEEBOT PRO K1VAC incorrectly implement authentication algorithm in Websocket communications. An unauthenticated attacker may connect and operate the affected robot.
CVE-2026-66411
Score 5.3 from GitHub Security Advisory published 2026-08-10. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
August 10, 2026
Last Modified
August 10, 2026
Advisory Details (2)
Auto-updated Aug 10, 2026JVNVU#92804348: Multiple vulnerabilities in DEEBOT PRO M1, DEEBOT PRO K1VAC and ECOVACS PRO App
https://jvn.jp/en/vu/JVNVU92804348/DEEBOT PRO M1/K1VAC ファームウェア更新のお知らせ (2026年3月31日更新) | ロボット紹介−ハロハスロボティクス
https://robot.hellohas.co.jp/news/update_20260331/Vendor Advisories for CVE-2026-66411(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 33× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 13:25 UTCGHSA enrichment
- 2026-08-18 15:38 UTCEG score recompute
- 2026-08-18 15:38 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 17:30 UTCEG score recompute
- 2026-08-17 17:30 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 19:52 UTCEG score recompute
- 2026-08-16 19:52 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-15 22:14 UTCEG score recompute
- 2026-08-15 22:14 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 00:36 UTCGHSA enrichment
- 2026-08-14 02:57 UTCEG score recompute
- 2026-08-14 02:57 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 05:19 UTCEG score recompute
- 2026-08-13 05:19 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 07:41 UTCEG score recompute
- 2026-08-12 07:41 UTCGHSA enrichment
- 2026-08-11 10:02 UTCEG score recompute
- 2026-08-11 10:02 UTCGHSA enrichment
Show 8 moreShow fewer
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 12:24 UTCEG score recompute
- 2026-08-10 12:24 UTCGHSA enrichment
- 2026-08-10 11:21 UTCEG score recompute
- 2026-08-10 11:21 UTCGHSA enrichment
- 2026-08-10 09:20 UTCEG score recompute
- 2026-08-10 08:16 UTCEG score recompute
- 2026-08-10 08:16 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-66411?
When was CVE-2026-66411 disclosed?
Is CVE-2026-66411 actively exploited?
What is the CVSS score of CVE-2026-66411?
How do I remediate CVE-2026-66411?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66411
Is Your Infrastructure Affected by CVE-2026-66411?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.