DJI robot vacuum hacked: 7,000 strangers' living rooms via a master key

Sun, 01 Mar 2026 00:00:00 +0100

A few days ago a press release turned up in my feed. I skim a lot of them every day – most I just scroll past. Not this one.

DJI. Robot vacuum. 7,000 strangers’ living rooms. A master key.

I read the article twice. And then I knew immediately: a follow-up video was needed.

The pattern that keeps repeating

If you’ve read my robot vacuum article, you might be nodding right now. Back then it was Ecovacs. Hacked robots remotely controlled in real time, chasing pets and shouting slurs through their speakers. I tried to explain back then why that wasn’t an absurd one-off incident, but a structural problem with this entire product category.

And now it’s happened again. Different manufacturer. Same category. Same fundamental vulnerability in principle.

This bothers me – not because I want to vilify robot vacuums, but because I believe most people who buy one simply don’t know what’s actually happening with their data. With the floor plan of their home. With camera footage, if the model has one. With the question of who, besides themselves, could theoretically access all of that.

What happened this time

It started innocuously. A French developer, a brand-new DJI robot vacuum, a free evening. The idea: control the robot around the apartment with a PS5 controller. Mario Kart in real life, but with dust bunnies.

To connect the controller, he needed the key from the app – nothing illegal, it was his own device. But when he used that key with the DJI server, the server didn’t just download his own data – it downloaded data from thousands of others. Over 7,000 robots across 24 countries. Battery levels, home floor plans, live camera feeds from strangers’ living rooms. The key wasn’t a normal key. It was a master key for the entire system.

DJI patched the vulnerability after it was reported. That’s good. But it doesn’t change the underlying picture.

Why I keep talking about this

After making this video I naturally asked myself whether I’m starting to get repetitive. Robot vacuums again. Privacy again. Same topic again.

But then I look at the comments under the old video. And I see how many people write that they simply hadn’t known how the technology behind it works. Not because they weren’t interested. But because hardly anyone explains it without immediately descending into panic or buzzwords.

That’s exactly what I want to do differently. No moralising, no fearmongering. Just: here are the facts. Here’s what they mean. And here are three concrete things you can do – if you want to. What you do with a camera-equipped robot vacuum in your home is your decision. I just want that decision to be an informed one.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

If you already have a view on this – or you have a robot vacuum at home and feel a quiet unease stirring – write it in the comments. I genuinely appreciate every perspective. And yes, every comment helps the video reach more people who are asking themselves exactly these questions for the first time.

Sources:

ESPHome Security Vulnerability: Critical CVE Affects All ESP32 Devices – Live Hack Demonstrates the Problem

Sun, 14 Sep 2025 00:00:00 +0200

A recently discovered security vulnerability in ESPHome 2025.8.0 affects ESP32 devices using the IDF Framework. The flaw allows attackers to bypass the built-in Basic Auth authentication and perform over-the-air updates without valid credentials.

This means: even if you have properly protected your ESPHome devices with a username and password, attackers can under certain circumstances still push firmware updates and gain control of the device.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

Practical Demonstration of the Security Vulnerability

ESPHome as a Popular DIY Solution

ESPHome has established itself as one of the most popular solutions for DIY smart home projects. Its simple integration of ESP32 and ESP8266 controllers into the smart home makes it a widely used tool in the community.

However, the recently discovered security vulnerability shows that even established software can have unexpected weaknesses. In the video, I demonstrate the practical exploitation of this flaw on a test device.

Live Demonstration of the Vulnerability

In the video, I perform a controlled test in which I bypass the authentication of an ESP32 device. I use command-line tools to send an HTTP request with an empty Authorization header.

The result: the ESP32 device accepts the firmware update even though no valid credentials were transmitted. The web server responds with “Update successful,” confirming that Basic Auth authentication is not working correctly in this version.

Who Is Affected? The Technical Details

ESPHome Version 2025.8.0 in Focus

The security vulnerability primarily affects ESPHome version 2025.8.0, though the official vulnerability description also mentions “possibly older versions.” Particularly critical: the flaw exclusively affects ESP32 devices using the IDF Framework.

In the video, I explain exactly why this combination is problematic and how to find out whether your devices are affected.

ESP32 vs ESP8266: An Important Distinction

There is some good news: ESP8266 controllers are NOT affected by this vulnerability. If you exclusively use ESP8266-based devices, you can breathe a little easier for now.

That said, caution is warranted: most modern ESPHome projects use ESP32 controllers, since they are significantly more powerful and offer more features. These popular controllers are the ones affected by the flaw.

The Attack in Detail: How the Hack Works

The Authorization Header as the Entry Point

What you see in the video is the practical exploitation of a vulnerability in HTTP Basic Authentication. Normally, attackers need to transmit valid credentials in the Authorization header. The security vulnerability, however, allows this protection to be bypassed with an empty header.

The hack works via the /update endpoint, which is normally used for over-the-air updates. An attacker can submit manipulated firmware to this endpoint and have it installed without authentication.

Potential Impact of the Vulnerability

Since the security vulnerability allows arbitrary firmware to be flashed, various attack scenarios are conceivable. An attacker could theoretically:

Capture and exfiltrate sensor data
Use the device for further network scanning
Preserve the original functionality to remain undetected
Make modifications to the firmware

The practical impact depends heavily on the individual network configuration and the security measures already in place.

Immediate Protective Measures: What You Need to Do NOW

Step 1: Update ESPHome

The most important step: update your ESPHome installation to version 2025.8.1 or newer immediately. These versions contain the fix for the critical security vulnerability.

In the video, I show you exactly where to find the current version and how to perform the update.

Step 2: Reflash All ESP32 Devices

Even more important: you must reflash all your ESP32 devices with the updated ESPHome version. Updating the ESPHome software alone is not enough – the firmware on the devices themselves must be updated.

The easiest way to do this is via the “Update” button in the ESPHome management interface. In the video, you can see the complete process and learn what to watch out for.

Step 3: When in Doubt, Update

If you are unsure whether your devices are affected: an update never hurts. It is better to update one time too many than to have a compromised device on your network.

Assessing the Security Vulnerability

Trust in Authentication Mechanisms

ESPHome users typically rely on the built-in Basic Auth authentication to protect their devices. This security vulnerability shows that even well-established authentication mechanisms can contain bugs.

Many users run their ESP32 devices for extended periods without regular updates, since they are considered stable and reliable. However, this approach can become problematic when newly discovered security vulnerabilities emerge.

Security on the Home Network

A common assumption is that devices on the internal network are automatically protected. This vulnerability makes clear, however, that attackers with network access – for example via compromised devices or a guest Wi-Fi network – can exploit security flaws too.

In the video, I discuss the importance of regular updates even for internally operated devices.

Lessons from the Security Vulnerability

Updates Are Not Optional

This vulnerability underscores once again: regular updates are not a tiresome chore, but critical to the security of your smart home. Even well-established software like ESPHome can suddenly develop critical flaws.

Defense in Depth

A single layer of protection – no matter how well implemented – is not enough. The ESPHome vulnerability shows that even authentication can fail. Additional layers of protection such as network segmentation or VPN access can make the difference when it matters.

What You Will Learn in the Video

The video offers far more than just theoretical knowledge. You will see:

Live hack demonstration – understand the threat through a practical walkthrough
Step-by-step update guide – learn how to update your devices correctly
Technical background – understand why this vulnerability is so dangerous
Preventive security measures – protect yourself against future threats
Community discussion – find out how others are dealing with the problem

The practical demonstration in the video illustrates how the vulnerability works and shows concretely how the authentication can be bypassed. This helps in understanding the technical details and assessing the risk for your own installation.

Your Role in Smart Home Security

Community Responsibility

Security vulnerabilities like this affect not only you personally, but the entire smart home community. Share your knowledge, inform other users, and make sure this important information reaches the people affected.

A Proactive Security Stance

Use this security vulnerability as an opportunity to rethink your overall smart home security. Which other devices have not received updates in a long time? Which systems rely too heavily on a single layer of protection?

Conclusion: Security Requires Continuous Attention

The ESPHome security vulnerability underscores the importance of regular updates even for established software. It shows that even proven solutions can have unexpected weaknesses.

The video demonstrates the practical exploitation of the vulnerability and explains the necessary protective measures – from immediate updates to preventive security strategies.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

→ In a follow-up article, I analyzed the community’s reaction to this vulnerability and address the question of whether ESPHome is still justifiable: ESPHome After the Security Vulnerability: Irresponsible or Still Worth It?

Note: Links marked with affiliate link are affiliate links. As an Amazon Associate I earn from qualifying purchases. This means I receive a small commission if you purchase through these links — at no extra cost to you. The revenue helps me run this blog and YouTube channel and keep creating content. Thank you for your support!
― Joachim

Security Vulnerability on Smart Home? Sure — But Secure!

DJI robot vacuum hacked: 7,000 strangers' living rooms via a master key

The pattern that keeps repeating

What happened this time

Why I keep talking about this

ESPHome Security Vulnerability: Critical CVE Affects All ESP32 Devices – Live Hack Demonstrates the Problem

Practical Demonstration of the Security Vulnerability

ESPHome as a Popular DIY Solution

Live Demonstration of the Vulnerability

Who Is Affected? The Technical Details

ESPHome Version 2025.8.0 in Focus

ESP32 vs ESP8266: An Important Distinction

The Attack in Detail: How the Hack Works

The Authorization Header as the Entry Point

Potential Impact of the Vulnerability

Immediate Protective Measures: What You Need to Do NOW

Step 1: Update ESPHome

Step 2: Reflash All ESP32 Devices

Step 3: When in Doubt, Update

Assessing the Security Vulnerability

Trust in Authentication Mechanisms

Security on the Home Network

Lessons from the Security Vulnerability

Updates Are Not Optional

Defense in Depth

What You Will Learn in the Video

Your Role in Smart Home Security

Community Responsibility

A Proactive Security Stance

Conclusion: Security Requires Continuous Attention