dbcve.org
Coros Pace 3 FirmwareOperating system · Yftech

CVE-2025-32880

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. With WLAN access, the COROS Pace 3 downloads firmware files via HTTP. However, the communication is not encrypted and allows sniffing and machine-in-the-middle attacks.

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 implements WLAN functionality for firmware downloads but uses unencrypted HTTP instead of HTTPS. An attacker on the same network can intercept (sniff) or manipulate (MITM) the firmware update traffic, potentially injecting malicious firmware into the device.

MitigationAvoid using the WLAN firmware update feature until COROS releases a patched firmware version that implements TLS-encrypted downloads; monitor vendor advisories for update availability.

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. Confirm COROS PACE 3 device
    Identify your smartwatch model. Verify it is a COROS PACE 3 device.
    Affected if Device is not a COROS PACE 3
  2. Check installed firmware version
    Open the COROS mobile app, navigate to Settings > Device > Firmware Version to view the current firmware. Compare this version number to 3.0808.0.
    Affected if Firmware version is 3.0808.0 or lower (equal to or less than the affected version)
  3. Verify WLAN firmware update is enabled
    Check if WLAN (WiFi) functionality is enabled on the device for firmware updates. Go to device settings and look for WLAN or WiFi settings used for firmware downloads.
    Affected if WLAN feature is enabled and configured for firmware updates

You are affected if you own a COROS PACE 3 with firmware version 3.0808.0 or lower and have the WLAN firmware update feature enabled on your device.

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.

From vendor data
Upgrade available Upgrade to a release after 3.0808.0
Interim mitigation

Avoid using the WLAN firmware update feature until COROS releases a patched firmware version that implements TLS-encrypted downloads; monitor vendor advisories for update availability.

Fix this in Coros Pace 3 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32880 — 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-32880 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