Skip to content
Applications

CVE-2026-66405

8.7
High
EPSS 0.28%Aug 10, 2026

High-severity CVE-2026-66405 with limited public details; potential remote code execution or unauthorized access.

common questions

Is CVE-2026-66405 being exploited?

Not confirmed. CVE-2026-66405 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-66405?

CVE-2026-66405 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-66405?

Not known from our data. No patch reference has been recorded for CVE-2026-66405, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-66405 affect?

CVE-2026-66405 affects Unknown (details blocked). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-66405?

Inventory assets, monitor vendor/NVD advisories, and apply vendor patches immediately when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Unknown (details blocked)
impact

May enable remote code execution, unauthorized access, or privilege escalation, leading to data theft or full system compromise if exploited.

action required

Immediate action required

affected versions
ECOVACS ROBOTICS DEEBOT PRO K1VAC
  • affected< V1.7.821
ECOVACS ROBOTICS DEEBOT PRO M1
  • affected< M1-1.7.27

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free