CVE-2025-32877: Improper Authentication
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate this vulnerability, European organizations and users should: 1) Monitor COROS official channels for firmware updates or patches addressing this issue and apply them promptly once available. 2) Restrict physical proximity access to the devices by enforcing policies that limit device use in unsecured or public environments where attackers could be nearby. 3) Disable BLE connectivity on the device when not in use to reduce exposure. 4) Use companion applications or device management tools that can enforce additional authentication or monitor BLE connections for suspicious activity. 5) Educate users about the risks of unauthorized BLE connections and encourage vigilance regarding unexpected device behavior or pairing requests. 6) Consider network segmentation and endpoint security controls to limit potential lateral movement if devices are connected to corporate networks. 7) For organizations using these devices in regulated environments, conduct risk assessments and implement compensating controls such as enhanced monitoring and incident response plans focused on BLE-related threats. 8) Explore alternative devices with stronger BLE security implementations if immediate patching is not feasible.
Description
An issue was discovered on COROS PACE 3 devices through 3.0808.0. It identifies itself as a device without input or output capabilities, which results in the use of the Just Works pairing method. This method does not implement any authentication, which therefore allows machine-in-the-middle attacks. Furthermore, this lack of authentication allows attackers to interact with the device via BLE without requiring prior authorization.