https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 28 May 2026 18:49:29 +0000 https://vulnerability.circl.lu/sighting/403877f7-6c1c-480b-9508-11082262fec7/export {"uuid": "403877f7-6c1c-480b-9508-11082262fec7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-32876", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/18972", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-32876\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 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.\n\ud83d\udccf Published: 2025-06-20T00:00:00.000Z\n\ud83d\udccf Modified: 2025-06-20T13:33:17.225Z\n\ud83d\udd17 References:\n1. https://syss.de\n2. https://support.coros.com/hc/en-us/articles/20087694119828-COROS-PACE-3-Release-Notes\n3. https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-023.txt", "creation_timestamp": "2025-06-20T14:43:51.000000Z"} {"uuid": "403877f7-6c1c-480b-9508-11082262fec7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-32876", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/18972", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-32876\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 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.\n\ud83d\udccf Published: 2025-06-20T00:00:00.000Z\n\ud83d\udccf Modified: 2025-06-20T13:33:17.225Z\n\ud83d\udd17 References:\n1. https://syss.de\n2. https://support.coros.com/hc/en-us/articles/20087694119828-COROS-PACE-3-Release-Notes\n3. https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-023.txt", "creation_timestamp": "2025-06-20T14:43:51.000000Z"} https://vulnerability.circl.lu/sighting/403877f7-6c1c-480b-9508-11082262fec7/export Fri, 20 Jun 2025 14:43:51 +0000