CVE-2026-96456 Reachy Mini Bluetooth PIN authentication can be bypassed by racing an authenticated device
Attackers can bypass Bluetooth PIN authentication by racing a legitimate user, gaining command access to the robot.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-96456?
CVE-2026-96456 is a medium-severity vulnerability in Pollen Robotics Reachy Mini, published on 23 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
The Reachy Mini Bluetooth service asks a connecting device for a PIN before it will accept commands. The check protects the session but not the caller, so an attacker in Bluetooth range can ride along on someone else's successful authentication.
The authenticated state is kept in a single shared flag on the service instance rather than per device. BlueZ passes the calling device's identity to the characteristic write handler in the options argument, but WriteValue(self, value, options) in src/reachy_mini/daemon/app/services/bluetooth/bluetooth_service.py ignores options entirely. The handler therefore has no idea which device sent a given write, and it cannot tell the authenticated one from any other.
Once any device completes the PIN exchange, the flag is set and every nearby device can send CMD_ commands until it resets. An attacker simply waits within radio range for a legitimate user to authenticate, then writes commands into the same window. No PIN is ever guessed or brute-forced.
This is the second step of a three-step chain that JFrog documented against the robot. The first is the unrestricted file upload in the media sounds API, tracked as CVE-2026-55419, which places an attacker-controlled script on the filesystem. This issue then provides command access over Bluetooth. The third is the Bluetooth command handler path traversal, tracked as CVE-2026-62661, which runs that script as root.
Which versions are affected by CVE-2026-96456?
How do I fix CVE-2026-96456?
No fix has been published for CVE-2026-96456 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-96456 being exploited?
There is no known exploitation of CVE-2026-96456 in the wild and no public exploit code.
Sources
Also known as GHSA-993g-hgjh-whmf, GHSA-w8hv-46m4-pm2j.