How to fix CVE-2025-32878?

Within 24 hours: Identify all COROS PACE 3 devices in use across the organization and restrict their network access to corporate WiFi until mitigation is confirmed. Within 7 days: Communicate with affected users to disable WLAN-based firmware updates and implement network segmentation to isolate smartwatch traffic. Within 30 days: Evaluate alternative smartwatch platforms without this vulnerability and develop a device replacement strategy; monitor for any unauthorized account access or token compromises among affected users.

Is Coros Pace 3 Firmware affected by CVE-2025-32878?

COROS PACE 3 smartwatches contain a critical vulnerability that allows attackers on the same network to intercept and manipulate firmware update communications, potentially stealing user account credentials and API tokens.

CVE-2025-32878

EUVD-2025-18754 CRITICAL

2025-06-20 [email protected]

9.8

CVSS 3.1

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 15, 2026 - 00:19 vuln.today

EUVD ID Assigned

Mar 15, 2026 - 00:19 euvd

EUVD-2025-18754

PoC Detected

Jul 08, 2025 - 14:32 vuln.today

Public exploit code

CVE Published

Jun 20, 2025 - 14:15 nvd

CRITICAL 9.8

Description

An issue was discovered on COROS PACE 3 devices through 3.0808.0. It implements a function to connect the watch to a WLAN. This function is mainly for downloading firmware files. Before downloading firmware files, the watch requests some information about the firmware via HTTPS from the back-end API. However, the X.509 server certificate within the TLS handshake is not validated by the device. This allows an attacker within an active machine-in-the-middle position, using a TLS proxy and a self-signed certificate, to eavesdrop and manipulate the HTTPS communication. This could be abused, for example, for stealing the API access token of the assigned user account.

Analysis

CVE-2025-32878 is a security vulnerability (CVSS 9.8). Risk factors: public PoC available.

Technical Context

CWE-295 (Improper Certificate Validation). CVSS 9.8 indicates critical severity with likely remote exploitation vector.

Affected Products

['Unspecified product']

Remediation

Monitor vendor channels for patch availability.

Priority Score

Low Medium High Critical

KEV: 0

EPSS: +0.1

CVSS: +49

POC: +20

CVE-2025-32878 vulnerability details – vuln.today

Back

CVE-2025-32878

CVSS Vector

Lifecycle Timeline

Tags

Description

Analysis

Technical Context

Affected Products

Remediation

Priority Score

Share

CVE-2025-32878

CVSS Vector

Lifecycle Timeline

Tags

Description

Analysis

Technical Context

Affected Products

Remediation

Priority Score

Share

External POC / Exploit Code