Robot control via anonymous MQTT topic access
Published May 7, 2026 · Updated May 7, 2026
Missing authentication in Yarbo Core Firmware 2.3.9 and earlier allows remote attackers on the same network to read telemetry and send controls. The embedded MQTT broker accepts anonymous clients and applies no topic-level read or write ACLs to telemetry and control topics. Network adjacency is the only gate; subscription exposes robot status and sensor data, while publication can drive movement or invoke other robot commands.
Summary
What happened
Missing authentication in Yarbo Core Firmware 2.3.9 and earlier allows remote attackers on the same network to read telemetry and send controls. The embedded MQTT broker accepts anonymous clients and applies no topic-level read or write ACLs to telemetry and control topics. Network adjacency is the only gate; subscription exposes robot status and sensor data, while publication can drive movement or invoke other robot commands.
The record
- CVE
- CVE-2026-7415
- Published
- May 7, 2026
- Updated
- May 7, 2026
- Vendor
- Yarbo
- Product
- Yarbo Core Firmware
- Classifications
- CWE-306, T1692.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2026CVE publishedPublication date reported by the CVE source.
- May 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.3.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Yarbo - NAT in my Back Yardproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo