# CVE-2026-66408: Hardcoded credentials in DEEBOT PRO K1VAC

> Attackers with physical access can obtain root credentials due to weak default passwords, enabling full device control and data access.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-qcc9-63j4-p26h

## What is CVE-2026-66408?

CVE-2026-66408 is a medium-severity vulnerability in ECOVACS ROBOTICS DEEBOT PRO K1VAC, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The root accounts of DEEBOT PRO M1 and DEEBOT PRO K1VAC are configured with weak passwords.
Physical access to an affected product may allow to obtain the password of the root account.

Weakness: CWE-1391 (Use of Weak Credentials)

## Which versions are affected by CVE-2026-66408?


## How do I fix CVE-2026-66408?

No fix has been published for CVE-2026-66408 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-66408 being exploited?

There is no known exploitation of CVE-2026-66408 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-66408 and fix it if it is affected.

What it is: CVE-2026-66408 is a medium-severity vulnerability in ECOVACS ROBOTICS DEEBOT PRO K1VAC, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66408 in the wild and no public exploit code.

Affected product: ECOVACS ROBOTICS DEEBOT PRO K1VAC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-66408/ (Markdown: https://insights.sbomify.com/CVE-2026-66408/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-66408
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-66408
- OSV: https://osv.dev/vulnerability/CVE-2026-66408

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-66408/
Summaries are generated and may contain mistakes; the official description above is the record.