Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessApproach target within Bluetooth range
-
DeliveryConnect to BLE command characteristic unpaired
-
ExploitCompute CRC-16/ARC checksum for command
-
ExecutionWrite spoofed notification payload
-
ImpactWatch vibrates and displays phishing alert
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to be within Bluetooth Low Energy radio range of the target BSW013 watch (AV:A - physical proximity, typically a few meters, not remote/internet-based). No pairing, authentication, or user interaction is needed (PR:N/UI:N), and the only integrity protection on the proprietary command characteristic is a CRC-16/ARC checksum, which is an error-detection code with no cryptographic security and is trivially recomputed by an attacker. Limiting factors: the attack targets one device at a time, requires physical proximity (cannot be conducted at scale or over the internet), and impact is confined to spoofed notification display and vibration (phishing/social-engineering) - it cannot read device data or cause denial of service. |
| Impact | This is a genuine but low-severity, narrow-impact issue rather than a high-priority emergency. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N) confirms the attack is adjacent (Bluetooth range only - NOT network-reachable), low-complexity, and requires no authentication or user interaction, consistent with the CWE-306 missing-authentication root cause and the 'unpaired attackers' language in the description. However, impact is deliberately scoped low: only VI:L (integrity) is set, with confidentiality (VC:N) and availability (VA:N) untouched - the attacker can spoof notification text and vibrate the watch, but cannot read data or disrupt the device, which is why the score lands at 5.3 (Medium). No EPSS score, SSVC decision, or KEV status was supplied in the input, so automatability and exploitation-in-the-wild signals cannot be evaluated. A public research/exploit repository is referenced (github.com/Pratham-16/fireboltt-Bsw013-BLE-vuln), indicating exploit code likely exists, but this is POC availability and must not be conflated with active exploitation. Net: the adjacency requirement (physical Bluetooth proximity, one target at a time) and phishing-only impact cap real-world risk far below what the 'unauthenticated/no-UI' metrics might suggest in isolation. |
| Exploit ScenarioDerived | An attacker within Bluetooth range of a victim's Fire-Boltt BSW013 watch (e.g., in a cafe, transit, or office) writes a crafted command to the proprietary BLE command characteristic without pairing, protected only by a trivially-computable CRC-16/ARC checksum. The watch vibrates and displays attacker-chosen alert text - for example a fake bank or delivery notification - to socially engineer the victim into a phishing action. Public research/exploit code appears to exist in the referenced GitHub repository, lowering the effort to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Notification injection in Fire-Boltt BSW013 smartwatches (firmware through V0.0.8) allows unpaired attackers within Bluetooth Low Energy range to send spoofed alerts and vibrate the device, enabling phishing via fake notifications. The vulnerability stems from missing authentication on a proprietary BLE command characteristic, with only a non-cryptographic CRC-16 checksum protecting commands. No public exploit code has been identified at the time of analysis, and the impact is limited to integrity (spoofed notifications) without confidentiality or availability loss.
RemediationAI
No vendor-released patch has been identified at the time of analysis. Users should monitor Fire-Boltt for firmware updates beyond V0.0.8 and apply them when available. As a compensating control, disable Bluetooth on the smartwatch when not in use to eliminate the attack vector; however, this disables all notification and companion app functionality. Additionally, avoid displaying sensitive information in notifications and be cautious of unexpected alerts, as the attack only spoofs notifications and does not compromise data. There is no way to restrict BLE access to trusted devices because the vulnerable characteristic lacks authentication, so physical proximity awareness is the only other mitigation, which is not a reliable technical control.
Affected VersionsENISA
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
The vulnerability is classified as CWE-306: Missing Authentication for Critical Function. The Fire-Boltt BSW013 smartwatch exposes a proprietary Bluetooth Low Energy (BLE) command characteristic that accepts write operations without any pairing or authentication checks. Attackers within radio range can send crafted BLE packets that include a valid CRC-16/ARC checksum-a simple error-detection code that provides no cryptographic protection and can be easily recomputed-to trigger vibration and display arbitrary notification text. The affected firmware versions are through V0.0.8. This design flaw allows spoofed notifications but does not permit reading device data, executing code, or causing denial of service.
Know when Bluetooth 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
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Adjacent BLE access (AV:A), no pairing/auth or interaction (PR:N/UI:N), low-complexity write; impact limited to spoofed notifications so I:L only, with no confidentiality or availability effect.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
Fire-Boltt BSW013 smartwatch firmware through V0.0.8 contains a missing authentication vulnerability that allows unpaired attackers to inject notifications by writing to the proprietary BLE command characteristic. Attackers within Bluetooth range can craft commands protected only by a CRC-16/ARC checksum to vibrate the watch and display spoofed alert text for phishing.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Unauthenticated Bluetooth Low Energy OTA firmware upgrade in the Meatmeet Pro WiFi & Bluetooth Meat Thermometer firmware
CVE-2025-32879 is a security vulnerability (CVSS 8.8) that allows an attacker. Risk factors: public PoC available.
Zephyr's Bluetooth Low Energy connection-response handler fails to verify that a connection request was actually initiat
Heap OOB write in Android Bluetooth driver via incorrect bounds check.
A use-after-free in the Android Bluetooth stack (bluetooth_ccc.cc, function BluetoothCccHandlerCallbackImpl) lets an att
Legacy pairing and secure-connections pairing authentication in Bluetooth BR/EDR Core Specification v5.2 and earlier may
Memory corruption in the Zephyr RTOS LE Audio Broadcast Sink (subsys/bluetooth/audio/bap_broadcast_sink.c) lets an attac
A memory leak combined with a use-after-free in the Linux kernel's Bluetooth HCI connection-setup path can crash the ker
A race condition in the Linux kernel's Bluetooth L2CAP subsystem allows a use-after-free of the hci_conn::l2cap_data poi
Bluetooth authentication bypass in SwitchBot Door Lock Series allows an attacker within BLE range to manipulate the lock
Out-of-bounds read in the Linux kernel Bluetooth subsystem's eir_get_service_data() leaks kernel heap memory into usersp
Use-after-free in the Linux kernel Bluetooth L2CAP stack lets a Bluetooth-adjacent attacker corrupt kernel memory by rac
EUVD-2026-97893
GHSA-hf79-56cq-w4qp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB