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

> Attackers can execute arbitrary commands and intercept data on Pebble Prism Ultra devices via unauthenticated Bluetooth Low Energy connections.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/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:** 4 Mar 2026
- **Updated:** 4 Mar 2026

## What is CVE-2025-69969?

CVE-2025-69969 is a critical missing authorization vulnerability in n/a, published on 4 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A lack of authentication and authorization mechanisms in the Bluetooth Low Energy (BLE) communication protocol of SRK Powertech Pvt Ltd Pebble Prism Ultra v2.9.2 allows attackers to reverse engineer the protocol and execute arbitrary commands on the device without establishing a connection. This is exploitable over Bluetooth Low Energy (BLE) proximity (Adjacent), requiring no physical contact with the device. Furthermore, the vulnerability is not limited to arbitrary commands but includes cleartext data interception and unauthenticated firmware hijacking via OTA services.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Pebblepower Pebble Prism Ultra Firmware.

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

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

## Is CVE-2025-69969 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69969 is a critical missing authorization vulnerability in n/a, published on 4 Mar 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-69969 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-69969/ (Markdown: https://insights.sbomify.com/CVE-2025-69969/index.md)
```

## Sources

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

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