CVE-2024-12078

CVE-2024-12078 is a medium-severity vulnerability in Ecovacs Deebot N10 Firmware with a CVSS 3.x base score of 6.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-321.

Key facts

Description

ECOVACS robot lawn mowers and vacuums use a shared, static secret key to encrypt BLE GATT messages. An unauthenticated attacker within BLE range can control any robot using the same key.

Frequently asked questions

What is CVE-2024-12078?
ECOVACS robot lawn mowers and vacuums use a shared, static secret key to encrypt BLE GATT messages. An unauthenticated attacker within BLE range can control any robot using the same key.
How severe is CVE-2024-12078?
CVE-2024-12078 has a CVSS 3.x base score of 6.3, rated medium severity. It is exploitable over an adjacent network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2024-12078 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-12078?
CVE-2024-12078 primarily affects Ecovacs Deebot N10 Firmware. In total, 14 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-12078?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-12078 have an EU (EUVD) identifier?
Yes. CVE-2024-12078 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-50576.
When was CVE-2024-12078 published?
CVE-2024-12078 was published on 2025-01-23 and last updated on 2026-06-17.

References

Affected products (14)

More vulnerabilities in Ecovacs Deebot N10 Firmware

All CVEs affecting Ecovacs Deebot N10 Firmware →

Other CWE-321 vulnerabilities

Browse all CWE-321 vulnerabilities →