CVE-2025-32877

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

CVE-2025-32879

An issue was discovered on COROS PACE 3 devices through 3.0808.0. It starts advertising if no device is connected via Bluetooth. This allows an attacker to connect with the device via BLE if no other device is connected. While connected, none of the BLE services and characteristics of the device...

CVE-2025-48705

An issue was discovered in COROS PACE 3 through 3.0808.0. Due to a NULL pointer dereference vulnerability, sending a crafted BLE message forces the device to reboot...

CVE-2025-48706

An issue was discovered in COROS PACE 3 through 3.0808.0. Due to an out-of-bounds read vulnerability, sending a crafted BLE message forces the device to reboot...

CVE-2025-48705

An issue was discovered in COROS PACE 3 through 3.0808.0. Due to a NULL pointer dereference vulnerability, sending a crafted BLE message forces the device to reboot...

CVE-2025-32879

An issue was discovered on COROS PACE 3 devices through 3.0808.0. It starts advertising if no device is connected via Bluetooth. This allows an attacker to connect with the device via BLE if no other device is connected. While connected, none of the BLE services and characteristics of the device...

CVE-2025-32876

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

CVE-2025-48705

An issue was discovered in COROS PACE 3 through 3.0808.0. Due to a NULL pointer dereference vulnerability, sending a crafted BLE message forces the device to reboot...

PT-2025-26316 · Coros · Coros Pace 3

Name of the Vulnerable Software and Affected Versions: COROS PACE 3 versions 3.0808.0 and earlier Description: The issue is caused by a NULL pointer dereference vulnerability. Sending a crafted BLE message can force the device to reboot. Recommendations: For COROS PACE 3 versions 3.0808.0 and...

PT-2025-26321 · Coros · Coros Pace 3

Name of the Vulnerable Software and Affected Versions: COROS PACE 3 versions through 3.0808.0 Description: An issue was discovered that affects the Bluetooth pairing method of the device. It identifies itself as a device without input or output capabilities, resulting in the use of the Just Works...

CVE-2025-32876

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

CVE-2025-48705

CVE-2025-48705 affects COROS PACE 3 up to version 3.0808.0. The issue is caused by a NULL pointer dereference when processing a crafted BLE message, which can force the device to reboot. In the provided sources, there is no explicit patch version or official fix detail. A reported workaround from...

PT-2025-26313 · Coros · Coros Pace 3

Name of the Vulnerable Software and Affected Versions: COROS PACE 3 devices versions through 3.0808.0 Description: An issue was discovered in the BLE implementation of the COROS smartwatch, which does not support LE Secure Connections and instead enforces BLE Legacy Pairing. In this pairing metho...

CVE-2025-32879

An issue was discovered on COROS PACE 3 devices through 3.0808.0. It starts advertising if no device is connected via Bluetooth. This allows an attacker to connect with the device via BLE if no other device is connected. While connected, none of the BLE services and characteristics of the device...

CVE-2025-48705

An issue was discovered in COROS PACE 3 through 3.0808.0. Due to a NULL pointer dereference vulnerability, sending a crafted BLE message forces the device to reboot...

CVE-2025-48706

An issue was discovered in COROS PACE 3 through 3.0808.0. Due to an out-of-bounds read vulnerability, sending a crafted BLE message forces the device to reboot...

CVE-2025-48706

The CVE-2025-48706 entry concerns COROS PACE 3 up to version 3.0808.0. Affected component: the device firmware handling Bluetooth Low Energy messages. Root cause: an out-of-bounds read in processing a crafted BLE message. Impact: when exploited, the device can reboot (availability impact) with co...

CVE-2025-32876

The CVE-2025-32876 issue affects COROS PACE 3 devices (through 3.0808.0). The BLE stack does not support LE Secure Connections and uses BLE Legacy Pairing, where the Short-Term Key can be easily guessed. The Temporary Key is 0 due to Just Works, enabling an attacker within Bluetooth range to snif...

CVE-2025-32879

An issue was discovered on COROS PACE 3 devices through 3.0808.0. It starts advertising if no device is connected via Bluetooth. This allows an attacker to connect with the device via BLE if no other device is connected. While connected, none of the BLE services and characteristics of the device...

PT-2025-25246 · Autel · Autel Maxicharger Ac Wallbox Commercial

Name of the Vulnerable Software and Affected Versions: Autel MaxiCharger AC Wallbox Commercial affected versions not specified Description: The issue concerns a misinterpretation of input in the ble process esp32 msg function. No information is provided about the estimated number of potentially...