What is the CVSS score of CVE-2025-69969?

CVE-2025-69969 has a CVSS 3.1 base score of 9.6 (Critical). CVSS vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2025-69969?

Yes, a public proof-of-concept exploit is available for CVE-2025-69969. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2025-69969?

Within 24 hours: Inventory all Pebble Prism Ultra v2.9.2 devices and isolate them from critical network segments; notify affected teams to discontinue use pending remediation. Within 7 days: Evaluate vendor's interim security guidance and assess alternative device solutions; implement network-level monitoring for unauthorized BLE communications. Within 30 days: Deploy replacement devices from vendor or alternate manufacturer once security patches are released and validated, or decommission affected units if no patch timeline is provided.

Pebble Prism Ultra Firmware CVE-2025-69969

CRITICAL

Missing Encryption of Sensitive Data (CWE-311)

2026-03-04 cve@mitre.org

RCE Information Disclosure Pebble Prism Ultra Firmware

9.6

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-311 OWASP Top 10:2025 A06:2025 - Insecure Design ASVS 5.0 V14 - Data Protection Encryption of sensitive data
Impact	CVSS 9.6. Smartwatch health data exposure.
Exploit ScenarioDerived	Intercept BLE communications without authentication.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Missing BLE authentication in Pebble Prism Ultra smartwatch. PoC available.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:05 CVSS 9.6

Unauthenticated BLE access in Pebble smartwatch.

RemediationAI

Apply firmware update.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-311 missing encryption in BLE communication.

Know when Pebble Prism Ultra Firmware gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 9.6 CRITICAL

AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

PoC Detected

Mar 09, 2026 - 17:26 vuln.today

Public exploit code

CVE Published

Mar 04, 2026 - 17:16 nvd

CRITICAL 9.6

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A critical vulnerability in Pebble Prism Ultra v2.9.2 devices allows attackers to remotely execute arbitrary commands without authentication, with active public exploits already available. Any organization deploying these devices faces immediate risk of unauthorized control, data breach, and potential physical security compromise.

Business Impact: Severe

Compensating Controls

Disable BLE connectivity on affected devices if operationally feasible; implement strict network segmentation isolating Pebble devices to dedicated, air-gapped networks with no access to critical systems; deploy continuous BLE traffic monitoring to detect anomalous command patterns; restrict physical proximity to devices through controlled access; maintain offline backups of critical configurations; contact vendor (SRK Powertech) immediately for emergency patching timeline and interim mitigation guidance.

Threat Intelligence Overview

EPSS Score

0.0%

Top 93% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

CRITICAL severity + public POC available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

Poc

System Exposure· derived

Controlled

Automatable· derived

Human Impact

Very High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +48

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Remote Code Execution CRITICAL

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.