How severe is CVE-2025-32876?

CVE-2025-32876 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over an adjacent network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2025-32876 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-32876?

CVE-2025-32876 affects Yftech Coros Pace 3 Firmware. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-32876?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-32876 have an EU (EUVD) identifier?

Yes. CVE-2025-32876 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-18749.

When was CVE-2025-32876 published?

CVE-2025-32876 was published on 2025-06-20 and last updated on 2026-06-17.

CVE-2025-32876

CVE-2025-32876 is a medium-severity vulnerability in Yftech Coros Pace 3 Firmware with a CVSS 3.x base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-306.

Key facts

Severity: Medium (CVSS 3.x base score 6.8)
EPSS exploit prediction: 0% (26th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-18749
Weakness: CWE-306
Affected product: Yftech Coros Pace 3 Firmware
Published: 2025-06-20
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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 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.
How severe is CVE-2025-32876?: CVE-2025-32876 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over an adjacent network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-32876 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-32876?: CVE-2025-32876 affects Yftech Coros Pace 3 Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-32876?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-32876 have an EU (EUVD) identifier?: Yes. CVE-2025-32876 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-18749.
When was CVE-2025-32876 published?: CVE-2025-32876 was published on 2025-06-20 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:o:yftech:coros_pace_3_firmware:*:*:*:*:*:*:*:*

More vulnerabilities in Yftech Coros Pace 3 Firmware

CVE-2025-32880 — Critical (CVSS 9.8): An issue was discovered on COROS PACE 3 devices through 3.0808.0. It implements a function to connect the watch to a…
CVE-2025-32878 — Critical (CVSS 9.8): An issue was discovered on COROS PACE 3 devices through 3.0808.0. It implements a function to connect the watch to a…
CVE-2025-32877 — Critical (CVSS 9.8): An issue was discovered on COROS PACE 3 devices through 3.0808.0. It identifies itself as a device without input or…
CVE-2025-48706 — Critical (CVSS 9.1): An issue was discovered in COROS PACE 3 through 3.0808.0. Due to an out-of-bounds read vulnerability, sending a crafted…
CVE-2025-32879 — High (CVSS 8.8): An issue was discovered on COROS PACE 3 devices through 3.0808.0. It starts advertising if no device is connected via…
CVE-2025-48705 — High (CVSS 7.5): An issue was discovered in COROS PACE 3 through 3.0808.0. Due to a NULL pointer dereference vulnerability, sending a…

All CVEs affecting Yftech Coros Pace 3 Firmware →

Other CWE-306 (Missing Authentication for Critical Function) vulnerabilities

CVE-2026-54309 — Critical (CVSS 10.0): n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, when @n8n/mcp-browser is run in HTTP…
CVE-2026-50242 — Critical (CVSS 10.0): In JetBrains Hub before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429…
CVE-2026-49257 — Critical (CVSS 10.0): mcp-pinot is a Python-based Model Context Protocol (MCP) server for interacting with Apache Pinot. In versions 3.0.1…
CVE-2026-46846 — Critical (CVSS 10.0): Vulnerability in the Oracle WebCenter Portal product of Oracle Fusion Middleware (component: Security Framework).…
CVE-2026-46803 — Critical (CVSS 10.0): Vulnerability in the Oracle WebCenter Portal product of Oracle Fusion Middleware (component: Security Framework).…
CVE-2026-46800 — Critical (CVSS 10.0): Vulnerability in the Oracle WebCenter Sites product of Oracle Fusion Middleware (component: WebCenter Sites).…

Browse all CWE-306 (Missing Authentication for Critical Function) vulnerabilities →