CyberSecBulletin

Yarbo vulnerabilities

We track 5 vulnerabilities in Yarbo products across 5 products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on June 12, 2026.

5vulnerabilities
4critical
1high
0exploited
9.5average CVSS score

Latest Yarbo vulnerabilities

  • 8.1 High severity

    Yarbo Android/IOS mobile application: Missing Authorization

    CVE-2026-7368Yarbo

    The Yarbo cloud does not enforce per-device or per-user authorization. Any client possessing valid credentials, whether the shared hard-coded credentials or legitimate per-user credentials, can subscribe to wildcard topics covering all robots globally, and can

  • 9.8 Critical severity

    Yarbo Android/IOS mobile application: Use of Hard-coded Credentials

    CVE-2026-10557Yarbo

    The Yarbo Android and iOS applications contain hard-coded MQTT broker credentials that are identical for all users and all devices. These credentials are embedded in the application binary and are readily extractable via APK decompilation. The credentials prov

  • 9.8 Critical severity

    Firmware: Missing Authentication for Critical Functionality

    CVE-2026-7415Yarbo

    The MQTT broker embedded in Yarbo firmware v2.3.9 is configured to allow anonymous connections with no topic-level read or write ACLs. Any host on the same network can subscribe to sensitive telemetry topics or publish control messages directly to the robot wi

  • 9.8 Critical severity

    Firmware: Use of Hard-coded Credentials

    CVE-2026-7414Yarbo

    Yarbo firmware v2.3.9 contains hardcoded administrative credentials embedded in the firmware image. These credentials are identical across all devices running this firmware and cannot be changed or removed by end users, enabling trivial unauthorized access to

  • 9.8 Critical severity

    Firmware: Hidden Functionality

    CVE-2026-7413Yarbo

    A hidden, persistent backdoor was found in Yarbo firmware v2.3.9 that provides remote, unauthenticated (or weakly authenticated) access to privileged functionality. The backdoor is undocumented, cannot be disabled via user-facing settings, and survives factory