# CVE-2025-69821: Denial of service in n/a

> An attacker can cause a denial of service on the Beat XP VEGA Smartwatch via its Bluetooth Low Energy connection.

- **Severity:** High 7.4 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/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:** 22 Jan 2026
- **Updated:** 22 Jan 2026
- **Also known as:** GHSA-357j-8mx4-39cc

## What is CVE-2025-69821?

CVE-2025-69821 is a high-severity denial of service vulnerability in n/a, published on 22 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in Beat XP VEGA Smartwatch (Firmware Version - RB303ATV006229) allows an attacker to cause a denial of service via the BLE connection

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Beatxp Vega Smartwatch Firmware.

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

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

## Is CVE-2025-69821 being exploited?

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

Public exploit code:

- A security assessment of the Beat XP VEGA Smartwatch (Firmware RB303ATV006229) focused on Bluetooth Low Energy (BLE) connectivity revealed a design and implemen tation weakness that enables a nearby BLE central device to establish and retain the single available BLE session without authentication or session access control. (github_poc): https://github.com/CipherX1802/CVE-2025-69821-Beat-XP-Vega-Smartwatch-Security-Assessment

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69821 is a high-severity denial of service vulnerability in n/a, published on 22 Jan 2026. 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-69821 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-69821/ (Markdown: https://insights.sbomify.com/CVE-2025-69821/index.md)
```

## Sources

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

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