CISA flags Yarbo flaws that expose global robot fleet
The uncomfortable part is the cloud authorization model: one valid credential can see and command devices well beyond one customer.
TL;DR
The Cybersecurity and Infrastructure Security Agency disclosed two Yarbo Android/iOS app and cloud MQTT flaws, CVE-2026-10557 and CVE-2026-7368, affecting versions before app 3.17.4 and all Yarbo cloud MQTT infrastructure. Commercial facilities using Yarbo robots face worldwide fleet exposure: extracted app credentials, or any breached valid credential, can subscribe to global telemetry and publish commands by serial number. Yarbo’s server-side authorization fix is not due until May 2026.
CISA’s advisory is a small document with a large blast radius. Yarbo’s Android and iOS mobile apps contain hard-coded MQTT broker credentials, identical across users and devices, embedded in the application binary and extractable through APK decompilation. Those credentials reach cloud MQTT brokers carrying real-time telemetry for the entire global Yarbo robot fleet and allow wildcard subscription to telemetry topics and publishing to command topics using a robot serial number. That is CVE-2026-10557, scored 9.8 critical under CVSS 3.1.
The second flaw, CVE-2026-7368, is the more durable problem. CISA says Yarbo’s cloud does not enforce per-device or per-user authorization. Even if the shared app credential goes away, any client with valid credentials, including a compromised legitimate user credential, can subscribe to wildcard topics covering all robots globally and publish to any robot’s command topic using only a serial number disclosed in telemetry. The app update to 3.17.4 removes one obvious failure mode. It does not, by itself, prove the authorization boundary exists.
Yarbo says server-side broker authorization will be enforced automatically with a May 2026 update and that no user action is required. Until then, commercial facilities using these robots have the awkward version of an operational technology problem: the asset may look like facilities equipment, but the control plane is a consumer-grade mobile app and a shared cloud broker. CISA lists the affected sector as Commercial Facilities and deployment as worldwide, which is exactly why assessors, state CISOs, and C3PAOs reviewing facility and operational technology exposure should not treat this as a niche robot bug.
The broader signal is that CISA’s Industrial Control Systems advisory lane is no longer only about programmable logic controllers, supervisory control and data acquisition systems, and plant-floor equipment with familiar industrial pedigrees. A cloud-managed robotics fleet can create the same control consequence with a very different procurement story. Monday’s work is plain: update the Yarbo app to 3.17.4 or later, inventory where Yarbo robots are used, assume the cloud authorization gap remains until the May 2026 server-side change is actually deployed, and monitor for anomalous MQTT-driven behavior rather than waiting for the robot to look like traditional ICS.
Published ·Deep Fathom