Skip to main content
VulnerabilityPublished

CVE-2026-7368: Yarbo Android/IOS mobile application · Missing Authorization

Affects Yarbo Android/IOS mobile applicationSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 3.17.4 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.17.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Yarbo Android/IOS mobile application to 3.17.4.

Affected software

ProductAffectedFixed in
YarboYarbo Android/IOS mobile applicationAffected
  • <3.17.4
Fixed in
  • 3.17.4
YarboYarbo Cloud MQTT infrastructureAffected
  • =All
Fixed in–

AI-suggested

If you cannot patch yet, restricting credential distribution and monitoring for unusual access patterns may help reduce risk.

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.

References

Community reviews

Loading reviews…