CVE-2026-55419 Reachy Mini: Unrestricted Upload of File with Dangerous Type
Unauthenticated attackers can upload arbitrary files to Reachy Mini robots, compromising data integrity and potentially enabling code execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-55419?
CVE-2026-55419 is a medium-severity vulnerability in pollen-robotics reachy_mini, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Reachy Mini is an SDK for controlling Reachy Mini robots. Prior to 1.8.2, the Reachy Mini daemon exposes the /api/media/sounds/upload endpoint implemented by the upload_sound method in src/reachy_mini/daemon/app/routers/media.py without authentication, file-extension checks, content validation, or size validation. The daemon binds to 0.0.0.0 by default and uses permissive CORS allow_origins=["*"], allowing an unauthenticated network attacker to upload arbitrary file types that are written to /tmp/reachy_mini_sounds/<original_filename>. Malicious files can compromise stored-data integrity and can serve as a foothold when combined with other vulnerabilities. This issue is fixed in version 1.8.2.
Weakness: CWE-434
Which versions are affected by CVE-2026-55419?
3 open source packages ship an affected version, including reachy-mini.
| Package | Affected | Fixed in |
|---|---|---|
reachy-mini PyPI | All versions | 1.8.2 |
reachy-mini PyPI | All versions | 1.8.2 |
reachy-mini PyPI | All versions | 1.8.2 |
How do I fix CVE-2026-55419?
Upgrade reachy-mini to 1.8.2 or later.
Is CVE-2026-55419 being exploited?
There is no known exploitation of CVE-2026-55419 in the wild and no public exploit code.
Sources
Also known as GHSA-m2pc-3q4q-w6jr, PYSEC-2026-3916.