dbcve.org
Coros Pace 3 FirmwareOperating system · Yftech

CVE-2025-32878

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-20
Fix available
A fix is available. Upgrade to after 3.0808.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The COROS PACE 3 smartwatch fails to validate X.509 server certificates during HTTPS requests when checking for firmware updates via WLAN. This allows a man-in-the-middle attacker with network proximity to intercept, eavesdrop, and manipulate HTTPS traffic using a self-signed certificate, potentially stealing user API access tokens.

MitigationAvoid connecting the device to untrusted WLAN networks until COROS releases a firmware update that properly validates TLS server certificates. Treat the device as untrusted on any network where an attacker could position themselves between the watch and the firmware API.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Coros Pace 3 FirmwareOperating system
Affected:<= 3.0808.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check if the device is a COROS PACE 3 smartwatch. Look at the device itself or check the device settings for model information.
    Affected if Device is not a COROS Pace 3, the vulnerability does not apply.
  2. Check installed firmware version
    On the COROS Pace 3, navigate to Settings > System > About > Version to view the firmware version number.
    Affected if Firmware version is 3.0808.0 or lower, indicating the device is affected.
  3. Verify WLAN firmware update feature
    Check if WLAN connectivity is enabled on the device. Navigate to Settings > WLAN or Settings > Connections > WLAN on the watch.
    Affected if WLAN is enabled and configured for firmware updates, the device is vulnerable when connected to untrusted networks.
  4. Assess network exposure
    Determine if the watch has connected or could connect to WLAN networks that are not fully trusted (public WiFi, shared networks, networks with unknown users).
    Affected if The device connects to WLAN networks where a man-in-the-middle attack is possible, the certificate validation flaw can be exploited.

If the device is a COROS Pace 3 with firmware version 3.0808.0 or lower and has WLAN enabled for firmware updates, the device is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.0808.0
Interim mitigation

Avoid connecting the device to untrusted WLAN networks until COROS releases a firmware update that properly validates TLS server certificates. Treat the device as untrusted on any network where an attacker could position themselves between the watch and the firmware API.

Recommended fix Moderate confidence

Firmware version > 3.0808.0 (check support.coros.com for the specific latest fixed release)

  1. Check the current firmware version on your Coros Pace 3 by opening the Coros app, selecting your device, and viewing the firmware version under Settings > Device Info
  2. Visit the official Coros support page at support.coros.com to check for available firmware updates
  3. If a firmware version newer than 3.0808.0 is available, connect your Coros Pace 3 to the charging cable and ensure the device has sufficient battery (above 50%)
  4. Open the Coros app and initiate the firmware update process from the device settings
  5. Allow the firmware update to complete fully without disconnecting the device from power and the app
Caveat Firmware updates are generally low-risk but ensure the device is connected to power during the update process to prevent bricking

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coros Pace 3 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing2.0 h
  • Review / QA4.0 h
14.0 hours of engineering $2,620
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32878 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32878 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data