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 provide access to cloud...
Vendor
Yarbo vulnerabilities
5 published CVES affecting Yarbo, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 4
- High
- 1
- Medium
- 0
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
- Firmware 3
- lawn mower firmware 3
- lawn mower pro firmware 3
- Yarbo Android/IOS mobile application 2
- Yarbo Cloud MQTT infrastructure 2
Latest Yarbo CVEs
Newest publication first
-
CriticalCVSS 9.3 EPSS 0.35%
-
CVE-2026-7368 Yarbo Android/iOS Mobile Application and Cloud Infrastructure Missing Authorization
PublishedHighCVSS 8.6 EPSS 0.26%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 publish to any robo...
-
CriticalCVSS 9.8 EPSS 0.54%
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 without authentication...
-
CriticalCVSS 9.8 EPSS 0.53%
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 device management in...
-
CriticalCVSS 9.8 EPSS 0.58%
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 reset and ordinary...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.