dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-32875

MEDIUM · 5.7 CVSS v3.1 Published 2025-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
No privileges

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 in the COROS application through 3.8.12 for Android. Bluetooth pairing and bonding is neither initiated nor enforced by the application itself. Also, the watch does not enforce pairing and bonding. As a result, any data transmitted via BLE remains unencrypted, allowing attackers within Bluetooth range to eavesdrop on the communication. Furthermore, even if a user manually initiates pairing and bonding in the Android settings, the application continues to transmit data without requiring the watch to be bonded. This fallback behavior enables attackers to exploit the communication, for example, by conducting an active machine-in-the-middle attack.

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 · moderate confidence

The COROS Android app (up to v3.8.12) and its companion watch device fail to enforce BLE pairing and bonding. Data transmitted via Bluetooth remains unencrypted, allowing attackers within range to eavesdrop. Even when users manually initiate pairing in Android settings, the application continues transmitting data without requiring a bonded connection, enabling active MITM attacks.

MitigationThe application must be updated to enforce BLE pairing/bonding before any data transmission. The watch firmware should also be updated to require bonding. The app should reject or encrypt data sent to unbonded devices.

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

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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Verify COROS app version
    Open Android Settings > Apps > COROS (or COROS Training) and note the version number displayed under App Info
    Affected if Version is 3.8.12 or lower (any version up to and including 3.8.12)
  2. Confirm BLE connectivity to watch
    Check if your COROS watch is paired via Bluetooth. Go to Settings > Bluetooth on Android and look for your paired COROS device, or observe the app shows a connected watch status
    Affected if BLE is enabled and the watch appears connected via Bluetooth on the Android device
  3. Check if bonded connection is required
    On Android, go to Settings > Bluetooth > tap the paired COROS watch device. Check if there is a 'Bonded' or 'Paired' status shown. Alternatively, in the COROS app, attempt to access features that transmit data (like workout sync) and observe if the app requires or indicates a bonded connection
    Affected if The watch shows as paired but the app does not enforce or require bonding before transmitting data (the app transmits unencrypted data regardless)
  4. Verify data transmission behavior
    Use a Bluetooth sniffing tool or monitor network/BLE traffic while using the COROS app to sync data or transmit commands to the watch. Observe if data is sent in plaintext without encryption
    Affected if Data is transmitted to the watch without encryption or without requiring a bonded BLE connection first

You are affected if you are using COROS Android app version 3.8.12 or lower and use BLE to communicate with your COROS watch, as the app does not enforce BLE bonding and transmits data unencrypted.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The application must be updated to enforce BLE pairing/bonding before any data transmission. The watch firmware should also be updated to require bonding. The app should reject or encrypt data sent to unbonded devices.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA8.0 h
62.0 hours of engineering $10,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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