Reachy Mini installed executable robot packages through an unauthenticated HTTP API

The Reachy Mini robot management interface accepted unauthenticated requests to install software from Hugging Face Spaces, with a permissive browser cross-origin configuration increasing reachability.

JFrog demonstrates installation of executable packages under the robot service authority. A robot being network-reachable is a prerequisite; the disclosure does not prove observed attacks against deployed owners.

The robot's HTTP management interface let a reachable client trigger installation of executable software from Hugging Face Spaces without a meaningful identity check. Its broad CORS configuration could also make a browser-based path relevant where the service was reachable from the user's network. The significant effect is replacement or addition of code under the robot's existing service authority. That does not by itself prove escape from the operating system or successful exploitation of an ordinary consumer device. JFrog's controlled demonstration establishes the install flow and its consequence, while a credible mitigation must secure both the installation endpoint and the package provenance independently.

Installing a Hugging Face Space is a code deployment operation, not merely fetching model content. If a reachable robot management API accepts that operation without caller authentication, the package runs with the service's authority once installed. Browser cross-origin policy can increase the attack surface but is not itself the source of execution permission. The separate Reachy Mini BLE case combines shared authentication state and a command path; the HTTP installer needs its own authorization and package provenance checks even after BLE is fixed.