CVE-2026-96455
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 7% of all known CVEs.
References
Related Vulnerabilities
Other CWE-306 (Missing Authentication for Critical Function) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-10271 | High | 7.5 | 100% | KEV + Ransom | - |
| CVE-2025-3248 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2023-42793 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2022-1388 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2023-21839 | High | 7.5 | 100% | KEV | - |
| CVE-2024-0012 | Critical | 9.8 | 100% | KEV + Ransom | - |
Common questions
How do I fix CVE-2026-96455?
No published fix for CVE-2026-96455 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-96455 being actively exploited?
Not that we know of. CVE-2026-96455 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.17% is the estimated probability that it will be exploited in the next 30 days. That is higher than 7% of all scored CVEs.
How severe is CVE-2026-96455?
CVE-2026-96455 has a CVSS v3 base score of 8.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-96455
Markdown
[](https://tridentstack.com/cve/CVE-2026-96455)HTML
<a href="https://tridentstack.com/cve/CVE-2026-96455"><img src="https://tridentstack.com/cve/badge/CVE-2026-96455.svg" alt="CVE-2026-96455"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-23.