CVE-2025-32876 Weak cryptography in n/a
Attackers within Bluetooth range can eavesdrop on COROS PACE 3 smartwatch communications due to weak BLE Legacy Pairing with a zero Temporary Key.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-32876?
CVE-2025-32876 is a medium-severity vulnerability in n/a, published on 20 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
An issue was discovered on COROS PACE 3 devices through 3.0808.0. The BLE implementation of the COROS smartwatch does not support LE Secure Connections and instead enforces BLE Legacy Pairing. In BLE Legacy Pairing, the Short-Term Key (STK) can be easily guessed. This requires knowledge of the Temporary Key (TK), which, in the case of the COROS Pace 3, is set to 0 due to the Just Works pairing method. An attacker within Bluetooth range can therefore perform sniffing attacks, allowing eavesdropping on the communication.
Weakness: CWE-306
Which versions are affected by CVE-2025-32876?
It affects 1 product.
Products include Yftech Coros Pace 3 Firmware.
How do I fix CVE-2025-32876?
No fix has been published for CVE-2025-32876 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-32876 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32876 exists.
Other vulnerabilities in n/a
Sources
Also known as GHSA-rvp9-hfhr-8ggg.