# CVE-2025-32879: Missing authorization in n/a

> Attackers can connect via Bluetooth to unpaired COROS PACE 3 devices and modify settings or install software without authentication.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-mqpq-5fv5-65gh

## What is CVE-2025-32879?

CVE-2025-32879 is a high-severity missing authorization vulnerability in n/a, published on 20 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on COROS PACE 3 devices through 3.0808.0. It starts advertising if no device is connected via Bluetooth. This allows an attacker to connect with the device via BLE if no other device is connected. While connected, none of the BLE services and characteristics of the device require any authentication or security level. Therefore, any characteristic, depending on their mode of operation (read/write/notify), can be used by the connected attacker. This allows, for example, configuring the device, sending notifications, resetting the device to factory settings, or installing software.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-32879?

It affects 1 product.


Products: Yftech Coros Pace 3 Firmware.

## How do I fix CVE-2025-32879?

No fix has been published for CVE-2025-32879 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-32879 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32879 exists.

## Other vulnerabilities in n/a

- [CVE-2025-32877](https://insights.sbomify.com/CVE-2025-32877/): Auth bypass in n/a (critical 9.8)
- [CVE-2025-32878](https://insights.sbomify.com/CVE-2025-32878/): Security feature bypass in n/a (critical 9.8)
- [CVE-2025-32880](https://insights.sbomify.com/CVE-2025-32880/): Other in n/a (critical 9.8)
- [CVE-2025-48706](https://insights.sbomify.com/CVE-2025-48706/): Denial of service in n/a (critical 9.1)
- [CVE-2025-48705](https://insights.sbomify.com/CVE-2025-48705/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32879 and fix it if it is affected.

What it is: CVE-2025-32879 is a high-severity missing authorization vulnerability in n/a, published on 20 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32879 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32879/ (Markdown: https://insights.sbomify.com/CVE-2025-32879/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32879
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32879
- OSV: https://osv.dev/vulnerability/CVE-2025-32879

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32879/
Summaries are generated and may contain mistakes; the official description above is the record.