How severe is CVE-2025-32877?

CVE-2025-32877 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-32877 being actively exploited?

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

What products are affected by CVE-2025-32877?

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

How do I fix CVE-2025-32877?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

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

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

When was CVE-2025-32877 published?

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

CVE-2025-32877

CVE-2025-32877 is a critical-severity vulnerability in Yftech Coros Pace 3 Firmware with a CVSS 3.x base score of 9.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-287.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 1% (46th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-18743
Weakness: CWE-287
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. 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.

Frequently asked questions

What is 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 attacks. Furthermore, this lack of authentication allows attackers to interact with the device via BLE without requiring prior authorization.
How severe is CVE-2025-32877?: CVE-2025-32877 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-32877 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (46th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-32877?: CVE-2025-32877 affects Yftech Coros Pace 3 Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-32877?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-32877 have an EU (EUVD) identifier?: Yes. CVE-2025-32877 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-18743.
When was CVE-2025-32877 published?: CVE-2025-32877 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-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…
CVE-2025-32876 — Medium (CVSS 6.8): An issue was discovered on COROS PACE 3 devices through 3.0808.0. The BLE implementation of the COROS smartwatch does…

All CVEs affecting Yftech Coros Pace 3 Firmware →

Other CWE-287 (Improper Authentication) vulnerabilities

CVE-2026-45480 — Critical (CVSS 10.0): Improper authentication in Azure Active Directory allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-46389 — Critical (CVSS 10.0): UDS Identity Config builds the Keycloak configuration image (realm, plugins, theme, truststore, JARs) consumed by UDS…
CVE-2026-10611 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in MISP when LDAP mixed authentication is enabled with OTP enforcement.…
CVE-2026-47280 — Critical (CVSS 10.0): Improper authentication in Azure Resource Manager (ARM) allows an unauthorized attacker to elevate privileges over a…
CVE-2026-42822 — Critical (CVSS 10.0): Improper authentication in Azure Local Disconnected Operations allows an unauthorized attacker to elevate privileges…
CVE-2026-20182 — Critical (CVSS 10.0): May 2026: This security advisory provides the details and fix information for a vulnerability that was discovered and…

Browse all CWE-287 (Improper Authentication) vulnerabilities →