Hundreds of thousands of internet-connected Shark robotic vacuums could also be weak to a essential distant code execution (RCE) flaw that would permit attackers to regulate units remotely, entry onboard cameras, retrieve residence maps, and doubtlessly steal saved Wi-Fi credentials.
An unbiased researcher disclosed this challenge following a 90-day reporting interval, and it arises from overly permissive AWS IoT Core MQTT insurance policies mixed with an embedded command-execution characteristic in Shark vacuum firmware.
Hundreds of thousands of Shark Robotic Vacuums Susceptible
The researcher examined the flaw on the Shark RV2320EDUS and AV1102ARUS fashions, noting that the vulnerability impacts all internet-connected Shark robotic vacuums utilizing the compromised provisioning configuration.
The reported assault chain begins with bodily entry to an affected system, enabling extraction of the device-specific AWS certificates and personal key from the system’s firmware.
These credentials grant extreme permissions on an AWS IoT MQTT dealer, enabling a compromised system to subscribe to wildcard matters that cowl different Shark units in the identical area.
Based on the report, a tool certificates taken from a weak RV2320EDUS vacuum might subscribe to the MQTT wildcard subject utilized by Shark units, exposing telemetry and command visitors for a lot of related vacuums.
The researcher claimed that the identical certificates might additionally publish messages to a different system’s AWS IoT Shadow subject if the goal’s serial quantity have been recognized. System serial numbers might allegedly be obtained instantly from uncovered MQTT visitors, thereby eradicating a major barrier to concentrating on arbitrary programs.
Probably the most extreme side of the vulnerability entails an Exec_Command discipline managed by the vacuum’s appd device-management daemon. Reverse engineering the binary revealed that the daemon parses specifically formatted MQTT messages and passes the offered command strings to a shell-execution perform.
An attacker who can publish a crafted desired-state replace to a goal system’s MQTT Shadow subject might trigger the vacuum to execute arbitrary instructions with excessive privileges, in response to the researcher.
The researcher confirmed the cross-device impression by utilizing credentials from one vacuum to execute a payload on a individually bought AV1102ARUS unit.
This profitable take a look at established that the vulnerability was not restricted to a single system or serial quantity. Whereas the proof of idea was executed solely on units owned by the researcher, the identical mechanism might theoretically be used towards uncovered units related to the affected dealer area.
The privateness and safety implications prolong past unauthorized cleansing instructions. Some Shark robotic vacuum fashions embrace cameras used for navigation and impediment detection, and the researcher said {that a} compromised system could possibly be used to entry a stay digicam feed and remotely management its motors.
Firmware evaluation additionally recognized domestically saved family mapping information and plaintext Wi-Fi pre-shared keys, doubtlessly offering attackers with a pathway from the vacuum to a sufferer’s broader residence community.
Throughout a 24-hour remark interval, the researcher reported processing greater than 10.5 million MQTT messages and figuring out roughly 1.52 million distinctive units in a single AWS area.
Of these, about 673,816 units, or 44%, despatched an Exec_Response message indicating help for the command execution functionality. The precise variety of weak units might range, as not all affected merchandise might have communicated in the course of the monitoring interval.
The disclosure timeline illustrates that SharkNinja was first contacted on March 11, 2026, with technical particulars shared on March 11.
After repeated follow-ups, the researcher publicly disclosed the difficulty on July 13, stating that no patch or confirmed remediation date had been offered. SharkNinja reportedly acknowledged the report was underneath evaluation and questioned whether or not a CVE was acceptable.
The researcher recommends that SharkNinja instantly limit AWS IoT insurance policies in order that system certificates can solely entry their very own MQTT matters, revoke or re-provision affected certificates, and take away or tightly authenticate the distant command execution performance.
Till an official repair is out there, homeowners ought to maintain vacuum firmware updated, isolate IoT units on a separate community the place doable, and monitor SharkNinja’s safety advisories for remediation steering.
Strengthen Your SOC by Accelerating Menace Detection & Fast Investigations. -> Combine ANY.RUN With Your SOC Now.
