CVE-2026-96456

What it is

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.

At a glance

Exploitability

Can be exploited from the same network segment without logging in, but needs a user to act. Limited direct impact.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-23 11:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-23 19:42 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 6.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-09-23 11:17 UTC

Last modified

2026-09-23 19:42 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-287 · Improper authentication

Record status

Deferred

Attack profile CVSS 3.1 · 6.3

Attack vector

Adjacent network

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-96456.md and follow it. Check whether this project is affected by CVE-2026-96456. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge