CVE-2026-96456
Received Received - Intake

Bluetooth Session Hijacking in Reachy Mini

Vulnerability report for CVE-2026-96456, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-23

Last updated on: 2026-09-23

Assigner: JFrog

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-23
Last Modified
2026-09-23
Generated
2026-09-23
AI Q&A
2026-09-23
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
jfrog media_sounds_api *
jfrog bluetooth_command_handler *
pollen_robotics reachy_mini *
pollen_robotics reachy_mini_sdk *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
CWE-287 When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves the Reachy Mini Bluetooth service which uses a shared authentication flag instead of per-device tracking. After one device authenticates via PIN, all nearby devices can send commands without authenticating. The service ignores device identity in Bluetooth write operations, allowing attackers within range to exploit an authenticated session without brute-forcing the PIN.

Detection Guidance

Monitor Bluetooth traffic near the Reachy Mini device for unauthorized command attempts after a legitimate user authenticates. Check if multiple devices can send CMD_ commands without re-authenticating. Use Bluetooth sniffing tools like hcidump or Wireshark to capture and inspect Bluetooth Low Energy (BLE) traffic for suspicious activity.

Impact Analysis

An attacker within Bluetooth range can take control of the robot after a legitimate user authenticates. They can send unauthorized commands without needing to guess or bypass the PIN. This could lead to unintended actions, data exposure, or further exploitation using linked vulnerabilities like file upload or command execution.

Compliance Impact

This vulnerability could violate compliance requirements for data protection and device security. Unauthorized access to a robot handling sensitive data may breach GDPR (privacy) or HIPAA (health data). The lack of proper authentication and authorization controls undermines security measures required by these standards.

Mitigation Strategies

Disable Bluetooth on the Reachy Mini when not in use. Restrict physical access to the robot's Bluetooth range. Update the firmware to a patched version if available. Implement additional authentication mechanisms beyond the shared flag to track devices individually.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-96456. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart