CVE-2026-7368: CWE-862 Missing Authorization in Yarbo Yarbo Android/IOS mobile application
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 robot's command topic using only the robot's serial number (disclosed in the telemetry stream). Even after removal of hard-coded credentials from the app, a single compromised credential could still provide fleet-wide access without per-device access controls.
AI Analysis
Technical Summary
The Yarbo cloud service does not enforce authorization on a per-device or per-user basis. Clients with valid credentials can subscribe to wildcard topics that cover all robots globally and publish commands to any robot's command topic by using the robot's serial number, which is exposed in telemetry data. This design flaw means that possession of any valid credential—whether shared hard-coded credentials or legitimate per-user credentials—enables broad unauthorized access to the entire fleet of robots. Even after removing hard-coded credentials from the application, the lack of per-device access controls allows a single compromised credential to provide fleet-wide control.
Potential Impact
An attacker with any valid credential can gain unauthorized access to all robots managed by the Yarbo cloud service. They can subscribe to all telemetry topics and send commands to any robot globally, potentially leading to unauthorized control or disruption of robot operations. This compromises confidentiality and integrity of the robot fleet's command and telemetry data. The vulnerability does not require user interaction and has low attack complexity, increasing the risk of exploitation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or remediation level is provided, users should monitor the vendor's announcements for updates. Until a fix is available, restricting credential distribution and monitoring for unusual access patterns may help reduce risk.
CVE-2026-7368: CWE-862 Missing Authorization in Yarbo Yarbo Android/IOS mobile application
Description
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 robot's command topic using only the robot's serial number (disclosed in the telemetry stream). Even after removal of hard-coded credentials from the app, a single compromised credential could still provide fleet-wide access without per-device access controls.
CVSS v4.0
Score 8.6high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Yarbo cloud service does not enforce authorization on a per-device or per-user basis. Clients with valid credentials can subscribe to wildcard topics that cover all robots globally and publish commands to any robot's command topic by using the robot's serial number, which is exposed in telemetry data. This design flaw means that possession of any valid credential—whether shared hard-coded credentials or legitimate per-user credentials—enables broad unauthorized access to the entire fleet of robots. Even after removing hard-coded credentials from the application, the lack of per-device access controls allows a single compromised credential to provide fleet-wide control.
Potential Impact
An attacker with any valid credential can gain unauthorized access to all robots managed by the Yarbo cloud service. They can subscribe to all telemetry topics and send commands to any robot globally, potentially leading to unauthorized control or disruption of robot operations. This compromises confidentiality and integrity of the robot fleet's command and telemetry data. The vulnerability does not require user interaction and has low attack complexity, increasing the risk of exploitation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or remediation level is provided, users should monitor the vendor's announcements for updates. Until a fix is available, restricting credential distribution and monitoring for unusual access patterns may help reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- icscert
- Date Reserved
- 2026-04-28T21:03:12.699Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c1a26e617e2d8347eb5bd
Added to database: 6/12/2026, 2:39:34 PM
Last enriched: 6/12/2026, 2:54:19 PM
Last updated: 6/12/2026, 3:44:06 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.