CVE-2026-96455
Received Received - Intake

Unauthenticated Remote Code Execution in Reachy Mini Robot

Publication date: 2026-09-23

Last updated on: 2026-09-23

Assigner: JFrog

Description
The Reachy Mini daemon exposes an HTTP API for managing the robot. Its app installation endpoint, POST /apps/install in src/reachy_mini/daemon/app/routers/apps.py, has no authentication. The handler's only dependency is Depends(get_app_manager), which just hands back the manager object from application state, so nothing in the chain ever checks a credential. The endpoint takes an AppInfo body naming a Hugging Face Space. The daemon downloads that Space and installs it as a Python package through install_package in src/reachy_mini/apps/sources/local_common_venv.py, using uv or pip. Installing a Python package runs the package's own build and setup code, so whoever chooses the Space chooses what code the robot runs. Anyone can publish a public Hugging Face Space, so this is not a meaningful restriction on the attacker. How far this reaches depends on the model. In _resolve_bind_host in src/reachy_mini/daemon/app/main.py the daemon binds 0.0.0.0 when it runs as the wireless version and 127.0.0.1 otherwise, with the vendor's own comment explaining that the robot has to be reachable on the LAN. On a wireless unit, then, any host on the same network can install and run code on the robot without credentials. One related change has already shipped but does not fix this. Version 1.8.2 replaced the wildcard CORS policy with an allow list of localhost and Tauri origins. That closes the browser drive-by route, where a web page the victim visits silently calls the endpoint in the background. It has no effect on this issue: CORS is enforced by browsers and governs whether script may read a response, while a direct HTTP request from another machine on the network involves no browser, no preflight and no CORS check at all.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-23
Last Modified
2026-09-23
Generated
2026-09-23
AI Q&A
2026-09-23
EPSS Evaluated
N/A
NVD
CVE-2026-96455
EUVD
EUVD-2026-85185

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
pollen_robotics reachy_mini 1.11.0
pollen_robotics reachy_mini 1.8.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-494 The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code.
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Reachy Mini robot exposes an unauthenticated HTTP API endpoint (POST /apps/install) that allows installing Python packages from Hugging Face Spaces without any credentials. The endpoint downloads and executes arbitrary code chosen by the attacker, as installing a Python package runs its build and setup scripts. On wireless units, the daemon binds to 0.0.0.0, making it accessible to any host on the same network.

Detection Guidance

Check if the Reachy Mini daemon is running on your system and listening on port 8000 or similar. Use commands like 'netstat -tulnp | grep python' or 'ss -tulnp | grep python' to identify listening ports. Verify if the endpoint POST /apps/install is accessible without authentication by sending a test request using curl: 'curl -X POST http://<robot-ip>:8000/apps/install -H "Content-Type: application/json" -d '{"name":"test"}''. If the request succeeds without credentials, the vulnerability is present.

Impact Analysis

An attacker on the same network as a wireless Reachy Mini robot can install malicious Python packages, gaining full control over the robot. This includes executing arbitrary code, modifying robot behavior, or accessing sensitive data. Even on non-wireless units, the risk exists if the daemon is exposed to untrusted networks.

Compliance Impact

This vulnerability allows unauthenticated remote code execution on the robot via the unauthenticated HTTP API, which could lead to unauthorized access to personal data processed by the robot. This may violate GDPR principles of data protection by design and default, as well as HIPAA requirements for safeguarding protected health information if the robot handles such data.

Mitigation Strategies

Immediately update the Reachy Mini software to the latest version, as newer releases may include patches. Restrict network access to the daemon by binding it to 127.0.0.1 instead of 0.0.0.0 in the configuration. Disable the HTTP API if not required or implement network-level firewalls to block unauthorized access. Monitor for suspicious activity on the robot's network interface.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-96455. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart