# CVE-2026-96455: Reachy Mini daemon allows unauthenticated remote code execution through the app installation endpoint

> Unauthenticated attackers on the network can install malicious Python packages via the app installation endpoint, leading to remote code execution on the robot.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-8w3q-4cmj-h32j

## What is CVE-2026-96455?

CVE-2026-96455 is a high-severity missing authorization vulnerability in Pollen Robotics Reachy Mini, published on 23 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-494 (Download of Code Without Integrity Check), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-96455?


## How do I fix CVE-2026-96455?

No fix has been published for CVE-2026-96455 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-96455 being exploited?

There is no known exploitation of CVE-2026-96455 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96455 and fix it if it is affected.

What it is: CVE-2026-96455 is a high-severity missing authorization vulnerability in Pollen Robotics Reachy Mini, published on 23 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96455 in the wild and no public exploit code.

Affected product: Pollen Robotics Reachy Mini. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-96455/ (Markdown: https://insights.sbomify.com/CVE-2026-96455/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96455
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96455
- OSV: https://osv.dev/vulnerability/CVE-2026-96455

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-96455/
Summaries are generated and may contain mistakes; the official description above is the record.